test: temporarily enable the bluez plugin and its tests

Until the bluez plugin is enabled by default, enable it manually in the
development flatpak and CI for testing purposes.

Also add two temporary ThreadSanitizer suppressions until they can be
fixed.

build-aux/flatpak/ca.andyholmes.Valent.Devel.Tests.json

@@ -18,6 +18,7 @@
         "--socket=session-bus",
         "--socket=ssh-auth",
         "--socket=wayland",
+        "--system-talk-name=org.bluez",
         "--system-talk-name=org.freedesktop.hostname1",
         "--system-talk-name=org.freedesktop.login1",
         "--system-talk-name=org.freedesktop.ModemManager1",
@@ -252,6 +253,7 @@
             "config-opts" : [
                 "--prefix=/app",
                 "--buildtype=debugoptimized",
+                "-Dplugin_bluez=true",
                 "-Dprofile=devel",
                 "-Dtests=true",
                 "-Dtracing=true"

build-aux/flatpak/ca.andyholmes.Valent.Devel.json

@@ -253,6 +253,7 @@
             "config-opts" : [
                 "--prefix=/app",
                 "--buildtype=debugoptimized",
+                "-Dplugin_bluez=true",
                 "-Dprofile=devel",
                 "-Dtests=true",
                 "-Dtracing=true"

tests/extra/tsan.supp

@@ -8,6 +8,10 @@
 #
 mutex:valent_device_get_type_once
 
+# src/plugins/bluez/valent-mux-io-stream.c
+race:valent_mux_io_stream_constructed
+race:valent_mux_io_stream_finalize
+
 # src/plugins/sms/valent-sms-store.c
 race:valent_sms_store_thread