gdb-remote test change coming up

Hey all,

I’m going to rework the startup of debugserver/lldb-gdbserver in the gdb-remote protocol tests to make use of the named-pipe mechanism of assigning an available listener port and communicating that back to the caller. Now that we have named pipe support in lldb-gdbserver, we can avoid a bit of randomness in port selection to avoid what creates occasional test failures due to port collisions. This will eliminate one source of non-relevant failure in those gdb-remote tests.

Hope to get that in over the next few days.