Mechanism to re-enable bluetooth autotests on Android hardware

CI is taking the Android-12 emulator in use, and unlike the older emulators, that emulator emulates also bluetooth. This has caused bluetooth autotests to fail, necessitating a skip on many of them. For example the test may wait for a bluetooth permission dialogue accept from the user.

We should still have an easy way to enable the bluetooth autotests locally when running on an actual hardware, something that the developer/tester could set. Something easier than commenting out each individual skips.

I'm not sure if there is a reasonable way to detect if we are running on hardware, nor can we rely on passing environment variables. It may be that some boolean flag needs to be set and the tests compiled with that.