Avoiding client-server version mismatch and setting `<quality>-<commit>` programmatically

[iSuslov]

Hey guys, thank you for this awesome project!

I've been exploring the remote server functionality, and I have a question regarding version compatibility between the client and server, as mentioned in the "Production concerns" section:

The commit and product quality should be the same on the client and on the server to be able to connect them. It can be an issue if you have the server deployed on a cluster, and the client is upgraded progressively: it is required for the server to expose both old and new version.

It can be achieved because all calls to the server are prefixed by <quality>-<commit>. So both servers can be started on a different port, and a reverse proxy in front of them can redirect the calls based on the path prefix.

My questions:

1. Can you provide a concrete example of how to set up the reverse proxy to handle multiple versions? How error prone is to trick vscode-server with such reverse proxy?

2. Is it possible to programmatically set the <quality>-<commit> on the client side? So we don't need a reverse proxy.

3. Are there any best practices or recommended approaches for managing version compatibility in a production environment where client and server updates may not always be simultaneous?

Thank you for your time and for maintaining this project.