android/tester: Adapter properties can come in any order
android/tester: Adapter properties can come in any order

There is no point in forcing specific order of adapter properties (with
exception of address being first).

mapfau/bluez,pkarasev3/bluez,pkarasev3/bluez,pkarasev3/bluez,mapfau/bluez,pstglia/external-bluetooth-bluez,pstglia/external-bluetooth-bluez,pstglia/external-bluetooth-bluez,silent-snowman/bluez,pstglia/external-bluetooth-bluez,ComputeCycles/bluez,pkarasev3/bluez,mapfau/bluez,ComputeCycles/bluez,silent-snowman/bluez,silent-snowman/bluez,silent-snowman/bluez,ComputeCycles/bluez,mapfau/bluez,ComputeCycles/bluez