Investigate compressing TS Server socket communication

Problem

On desktop, TS Server uses a json based protocol. This protocol up being quite verbose for larger documents, especially for requests such as navTree which return results from the entire file

Just opening checker.ts for example results in individual requests and responses that are a few MB in size.

Proposal

We've seen up to a 10x reduction of on the wire data by enabling websocket per-message compression for VS Code's internal communications. We aren't using web sockets here, but I believe we should be able to fairly easily compress individual messages on the server side and decompress them on the editor side. Most importantly, we could enable this without any changes to the json protocol itself.

For backwards compatibility, this would have to be an opt-in feature

Empieza rastreando la comunicación de sockets de TS Server entre el servidor y el editor, centrándote en el formato de mensajes JSON y en las respuestas navTree grandes. Revisa el enfoque propuesto de compresión por mensaje y su requisito de opt-in; se considera terminado cuando se reduce el tamaño transmitido sin cambiar el protocolo JSON ni romper los clientes sin compresión.