Improve experience and error reporting for distant launch

[chipsenkbeil]

Per #92, getting an error that says "No such file or directory" is fairly useless to users of the tool.

1. Error messages need to be more robust during launch
2. We may want to switch away from unix domain socket being the default choice as it may be more cumbersome for some
3. There's not an easy way to go from launch to action with environment variables, it may be handy to support an environment variable of DISTANT_SESSION that you can make from pipe that includes everything needed

[chipsenkbeil]

Done using anyhow errors that have context

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.