Remote Deployment: Facilitating Automatic Startup and Port Forwarding

[colin-grant-work]

Investigating remote deployments of this plugin, I've been doing some checking on VSCode utilities for Remote deployments and found the asExternalUri function in the env namespace. Basically, in a desktop deployment, that function does nothing, because external is the same as local, but in a remote deployment, that function transforms the URI into a form that the client can use to access a service running on the host and also does any port forwarding, if the application is set up for that. You can see it in action in the 'Live Preview' plugin, which, like the Trace Extension, opens up a server on the remote machine on certain ports.

With that in mind, it may be desirable to modify the handling of the preference for the trace server port, either here or in the VSCode Trace Server plugin.

The caveat that I can see is that, given that there are currently two preferences (one in the server plugin and one here) for the location of the server, it might be desirable to let the user use this plugin's preference raw to specify the exact shape of the URL they want the views to use locally so that the user can set up access to the service manually, but in an ideal world where there was only one preference specifying the server's behavior, the asExternalUri utility could be applied to it to automatically expose the necessary ports on remote machines.

Originally posted by @colin-grant-work in #158 (comment)