Support ADB_SERVER_SOCKET environment variable for remote adb connections

Consider the following scenario:

• Qt Creator is running on machine A
• An Android Virtual Device is running on machine B
• Qt Creator is supposed to deploy an APK to the AVD from machine B

adb supports such scenarios through the ADB_SERVER_SOCKET environment variable: On machine B, the following command can be run:

• adb -a -P <port> nodaemon server

Then on machine A, ADB_SERVER_SOCKET can be set as follows:

• ADB_SERVER_SOCKET=tcp:<Machine A host name or IP>:<port>

Running adb devices will then display the same output on machine A as on machine B, allowing adb on machine A to use the AVD from machine B.

Unfortunately, Qt Creator does not seem to support this environment variable so this sort of deployment scenario is not possible.

A possible real-world example for this scenario might be if Qt Creator is running on WSL while the AVD runs on the Windows host, but there are surely others as well.