WebBluetoothServices currently use BluetoothDispatcherHost to add themselves as observers to BluetoothAdapter. WebBluetoothServices should add/remove themselves to/from BluetoothAdapter directly.

We use testRunner.setBluetoothFakeAdapter() to set a fake adapter on the BluetoothDispatcherHost. Because WebBluetoothServices use BluetoothDispatcherHost, services get added as observers to the test adapter. We have the following options if we want WebBluetoothService to add themselves directly as observers and always observer the right adapter:

1. Make testRunner.setBluetoothFakeAdapter() set the fake adapter per frame rather than per process.
2. Implement dynamic adapters so that we no longer need to swap the adapter.
 

WebBluetoothServices currently use BluetoothAdapterFactoryWrapper to interact with the adapter and add themselves as observers.

BluetoothAdapterFactoryWrapper keeps a copy of a BluetoothAdapter and adds the WebBluetoothService as observer of the current adapter. When the adapter is swapped during tests, BluetoothAdapterFactoryWrapper removes the observers from the old adapter and adds them to the new adapter. When the WebBluetoothService wants to interact with the adapter it acquires this new test adapter.

Rather than using BluetoothAdapterFactoryWrapper to interact with BluetoothAdapter, WebBluetoothServices should acquire the adapter from BluetoothAdapterFactory directly. For this we need to use dynamic mocks so that we can remove the devices/services/characteristics/descriptors from the adapter itself rather than swapping it for another one.