Bug with remote servers

Hi, I've noticed an issue where cargo vibe fails when set to a remote address because it falls back to the in-process client. ``` ~/d/cargo-vibe (main) $ CARGO_VIBE_ADDR="ws://192.168.0.111:12345" cargo run [cargo-vibe] success! [cargo-vibe] starting in-process server [(0.4, 200ms)] [cargo-vibe] no devices found ``` In the case where the address is remote, cargo vibe should wait for the remote client to finish spawning and use that. I've made this PR with a possible solution. It doesn't perfectly check if the address is remote (like `not-a-localhost.example.com`) but it would catch most cases (can improve that if desired).