There is no "right" number of the timeout to wait for Android to finish turning on/off Bluetooth. Any number chosen will have a possibility that Android takes longer than that and that will cause Bluetooth to be turned off by itself bug ( https://crbug.com/843650 ). Therefore we should not rely on the time Android takes to finish the task, but instead the following is proposed:

* Remove the timeout to wait Android turning on/off Bluetooth.
* The Android side may never finish this task due to crash. Therefore we need to reset our pending/queue every time Android is restarted (by listening to arc bridge connection established event).
* The Android side may take forever to finish the task due to reasons other than crash. In this case the next turn on/off tasks will be stuck in our queue. This is okay since it will be also stuck in Android's side anyway if we send another task while the previous task is still in progress.
* To avoid our stuck queue to grow unlimited, modify our Bluetooth toggle queue to be a compressed queue: Queue that consists of only 1 "to-be-sent" task. Together with 1 "in-progress" task this is enough to prevent multiple tasks to be sent at the same.