Launch emulators sequentially

[d4vidi]

Is your feature request related to a problem? Please describe.
The Android emulator binary doesn't seem to handle many launches taking place at the same time very well. In particular, seems that emulator launches touch some of the configuration, and - if race conditions are met, that evidently causes some emulators either boot from scratch (overlook snapshots) due to an alleged config change or possibly boot with the wrong specs.

Note: This somewhat associates with the adb jam problem (#1857), as it is possible that as a side effect, improving the launch behavior would help reduce the frequency of "jams": as the tests-run timeline changes, it should become less likely that multiple adb install commands are executed simultaneously, which seems to be the soft spot of adb with respect to that specific bug.

Describe the solution you'd like
Make emulators launch as a mutually-excluded sequence.

Describe alternatives you've considered
N/A

Additional context
N/A

[d4vidi]

Following recent futile attempts at getting this to work properly, I'm "back-logging" it again with this possible change as the next potential PoC: Stop using the emulators' -read-only and clone emulator instances on-the-fly, instead (as implemented for iOS).

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you believe the issue is still relevant, please test on the latest Detox and report back.

Thank you for your contributions!

For more information on bots in this reporsitory, read this discussion.

[d4vidi]

Closing; We will revisit if necessary