feat: enable LSP (Language Server Protocol) infrastructure

This commit enables the complete LSP infrastructure that was previously
disabled in Phoenix. The LSP system provides a foundation for language
server integration supporting features like code completion, parameter
hints, jump to definition, find references, and diagnostics.

Changes:
- Enabled LSP initialization in ClientLoader.js by uncommenting
  initDomainAndHandleNodeCrash() call
- Enabled LSP unit tests in UnitTestSuite.js

The LSP infrastructure includes:
- Complete Language Client implementation with Node.js bridge
- Protocol adapter for LSP communication (JSON-RPC over IPC/stdio)
- Default providers for code hints, parameter hints, and navigation
- Support for all standard LSP features defined in ToolingInfo.json
- Test suite with mock language servers

This enables the platform for JavaScript/TypeScript and other language
server integrations. Language-specific clients can now be registered
using LanguageTools.initiateToolingService() API.

Author: claude

src/languageTools/ClientLoader.js

@@ -171,7 +171,7 @@ define(function (require, exports, module) {
             console.error("ClientInfo domain could not be loaded: ", err);
         });
     }
-    //initDomainAndHandleNodeCrash();
+    initDomainAndHandleNodeCrash();
 
 
     exports.initiateLanguageClient = initiateLanguageClient;

test/UnitTestSuite.js

@@ -143,6 +143,6 @@ define(function (require, exports, module) {
     // Node Tests
     require("spec/NodeConnection-test");
     // todo TEST_MODERN
-    // require("spec/LanguageTools-test"); LSP tests. disabled for now
+    require("spec/LanguageTools-test");
     // require("spec/Menu-native-integ-test"); evaluate after we have native menus in os installed builds
 });