Attempt at a better fix for OralB / LED BLE

It (tentatively) seems that adding some fake content to the "bluetooth"-
attribute prevents the config-flow from crashing.

custom_components/led_ble/manifest.json

@@ -4,5 +4,9 @@
   "version": "0.0.0",
   "config_flow": false,
   "integration_type": "device",
-  "bluetooth": []
+  "bluetooth": [
+    {
+      "local_name": "Foobar_*"
+    }
+  ]
 }

custom_components/oralb/manifest.json

@@ -4,5 +4,9 @@
   "version": "0.0.0",
   "config_flow": false,
   "integration_type": "device",
-  "bluetooth": []
+  "bluetooth": [
+    {
+      "local_name": "Foobar_*"
+    }
+  ]
 }

logger_filters.yaml

@@ -66,13 +66,6 @@ homeassistant.components.meater:
     ^Error requesting meater_api data: Cannot connect to host
   - >-
     ^Timeout fetching meater_api data
-# "Disabling" the OralB and LEB BLE integrations seems to have not removed their
-# "config_flow" registrations (see 070743) – not sure what's going on here (the
-# old settings probably got stuck somewhere); for now simply prevent the errors
-# this generates from getting logged...
-homeassistant.config_entries:
-  - >-
-    ^Error occurred loading flow for integration (oralb|led_ble):
 # Testing the "Eufy Security" custom-component; works, but keeps throwing these
 # when the camera-stream is not active – ignore this for now...
 homeassistant.components.stream.stream.camera.bonus_room: