Refactor GdbRemote test cases to support remote platforms
Previously these test cases execute lldb-server on the host and run the tests against it even if a remote platform was specified. With this CL these tests always test the communication with an lldb-server instance running on the target.
SBPlatform::Install used here also, but I think it is impossible to avoid, because these tests are testing LLGS in a lower level with sending packets directly to it.
The logic you mentioned is executed only when we do a "run" or a "process launch" command in lldb what isn't happening here. The inferior is launched with sending an $A packet directly to LLGS from python with skipping the logic surrounding it in lldb.