Fail gracefully if remote runner connection info is unreliable

[sourishkrout]

Unless any --insecure/--insecure=false/--insecure=true is explicitly set.

There is an edge case when VS Code resumes previously persisted terminal sessions upon loading which shows an ugly error if the server is now no longer running under the previously specified socket. In this case, it's better UX to gracefully fall back to a local runner.

PS: Stopped short of addressing gRPC upstream deprecations. Would like to tackle them as part of moving to runme beta cmds.

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
75.6% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud