fix: drop invalid .js extension from vscode-jsonrpc/node import

vscode-jsonrpc (bumped to ^9.0.1 in this PR) only exports the
'./node' subpath (not './node.js') per its package.json exports map,
so importing 'vscode-jsonrpc/node.js' failed at runtime with
'"./node.js" is not exported under the conditions [...]'. This broke
test/e2e/extension_env_access.e2e.test.ts on the nodejs ubuntu CI
jobs. Fixed to match every other import site in the SDK, which
already uses 'vscode-jsonrpc/node' without the extension.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: SteveSandersonMS

nodejs/test/e2e/extension_env_access.e2e.test.ts

@@ -13,7 +13,7 @@ import {
     createMessageConnection,
     StreamMessageReader,
     StreamMessageWriter,
-} from "vscode-jsonrpc/node.js";
+} from "vscode-jsonrpc/node";
 import { approveAll } from "../../src/index.js";
 import { getSdkProtocolVersion } from "../../src/sdkProtocolVersion.js";
 import { createSdkTestContext, isInProcessTransport } from "./harness/sdkTestContext.js";