Find out how to finish Go command bridge integration in Remote Linux

The Go command bridge works well with docker, and since  0dd875a7fb42 https://codereview.qt-project.org/c/qt-creator/qt-creator/+/611572 it is also used for Remote Linux (and derived cases).

However, it lacks handling of exceptional cases like devices being or becoming "unavailable" in contrast to the "always accessible" docker case, real devices and connections to them are not necessarily fully under the control of the user, currently leading to really bad user experience up to hard lockups of Qt Creator.

As a fundamental problem we have here that we (necessarily) need to have a lot of operations synchronously whereas user interaction or even just notification is (necessarily) asynchronous, and spinning the event loop for these notification can trigger unrelated update activities in other parts of the gui, which in turn may trigger other bridge accesses.

The task here is to come up with a plan on how to make the setup more robust, preferably without sacrificing the current ability to "just use" previously setup devices on a creator start.