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

Inizia tracciando la comunicazione socket di TS Server tra il server e l’editor, concentrandoti sul formato dei messaggi JSON e sulle risposte navTree di grandi dimensioni. Esamina l’approccio proposto alla compressione per messaggio e il relativo requisito di opt-in; il lavoro è completato quando la dimensione trasmessa viene ridotta senza modificare il protocollo JSON né compromettere i client non compressi.