Can we use the default host names?

Having the set of host names generated by the CLI (`coder.`) and the set of host names generated by the plugin (`coder-vscode.--*`) causes some confusion when you mix connecting via the remote SSH plugin and connecting through our plugin.

Basically, you can get a different set of settings and recents, because VS Code thinks they are different connections (the host names are different, after all).

I believe we do this for two reasons:

1. So we can use `vscodessh` instead of `ssh`.
2. To attach an environment variable that allows us to track the connection as a VS Code connection, and not just a regular SSH connection. (Which, by the way, means that connections done with the remote SSH plugin without our plugin will not be tracked as VS Code connections!)

The first is easily solved, the JetBrains plugin already uses the regular `ssh` command. I think we just have to port the network info command? And this would make it usable with JetBrains as well, so win-win.

The second is trickier. We need some way to identify the connection but I am not sure how. We could track the process on the remote instead, like we do with JetBrains?

Empieza rastreando cómo CLI y plugin generan nombres de host, y luego lee cómo el plugin de JetBrains utiliza el comando ssh normal y su comando de información de red. El trabajo estará terminado cuando ambas rutas de conexión puedan compartir los nombres de host predeterminados y, al mismo tiempo, identificar y rastrear las conexiones de VS Code.

Escrito por el modelo de indexación a partir del texto del issue.