fix: use vtsls for TypeScript completions with proper document lifecycle

Problem:
Completions popup showed global/project symbols instead of context-appropriate
completions (e.g., typing `x.` on a string showed `arguments`, `config` instead
of `charAt`, `toLowerCase`).

Root Cause:
The extension sent `textDocument/didOpen` every time `getHints()` was called,
violating LSP protocol and causing the server to reset its analysis state.

Changes:

1. Switch to vtsls language server (@vtsls/language-server)
   - Same LSP server that Zed editor uses by default
   - Wraps VS Code's TypeScript extension directly
   - Better server-side fuzzy matching and completion performance

2. Fix LSP document lifecycle (VS Code pattern)
   - Send `textDocument/didOpen` only once per document
   - Send `textDocument/didChange` for subsequent content updates
   - Track open documents in `openDocuments` Set
   - Track document versions in `documentVersions` Map

3. Add proper state cleanup
   - Clear tracking state on server restart (projectOpen)
   - Clear tracking state on shutdown
   - Clear tracking state on server exit
   - Send `textDocument/didClose` when documents are refreshed

4. Add vtsls-specific initialization options
   - Enable server-side fuzzy matching
   - Set completion entries limit to 5000
   - Enable auto-use of workspace TypeScript SDK

Author: charlypa

src-node/package-lock.json

@@ -19,14 +19,16 @@
     },
     "IMPORTANT!!": "Adding things here will bloat up the package size",
     "dependencies": {
+        "@expo/sudo-prompt": "^9.3.2",
         "@phcode/fs": "^3.0.1",
-        "open": "^10.1.0",
-        "npm": "10.1.0",
-        "ws": "^8.17.1",
+        "@vtsls/language-server": "^0.3.0",
+        "cross-spawn": "^7.0.6",
         "lmdb": "^2.9.2",
         "mime-types": "^2.1.35",
-        "cross-spawn": "^7.0.6",
+        "npm": "10.1.0",
+        "open": "^10.1.0",
+        "typescript": "^5.3.3",
         "which": "^2.0.1",
-        "@expo/sudo-prompt": "^9.3.2"
+        "ws": "^8.17.1"
     }
-}
+}