Fix VS Code integration tests on macOS

VS Code 1.131 removed the legacy Contents/MacOS/Electron compatibility
executable on macOS. Upgrade @vscode/test-electron to 3.1.0 so the test harness
resolves the executable from the application bundle metadata instead of trying
to launch the removed path.

Override jest-runner-vscode's transitive @vscode/test-electron dependency as
well. Its declared 2.x range would otherwise cause npm to install a private
2.5.2 copy and leave the runner using the broken executable lookup despite the
direct dependency upgrade.

Increase the minimal-workspace activation polling and Jest timeouts because
extension activation under VS Code 1.131 can take longer on macOS than the
previous 30-second allowance. This preserves the activation assertion while
avoiding a deterministic timeout on slower macOS hosts.

These failures were observed only in local macOS runs. GitHub Actions runs the
VS Code integration suite on Linux and Windows, where the existing tests were
passing.

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

Copilot-Session: d7e3c611-18b2-4bf2-8f9a-09e7a8d1ef8e

Author: cklin

extensions/ql-vscode/package-lock.json

@@ -2149,7 +2149,7 @@
     "@types/yauzl": "^3.4.0",
     "@typescript-eslint/eslint-plugin": "^8.65.0",
     "@typescript-eslint/parser": "^8.65.0",
-    "@vscode/test-electron": "^2.5.2",
+    "@vscode/test-electron": "^3.1.0",
     "@vscode/vsce": "^3.9.2",
     "ansi-colors": "^4.1.1",
     "applicationinsights": "^2.9.8",
@@ -2198,7 +2198,10 @@
     "d3-graphviz": {
       "@hpcc-js/wasm": "2.30.0"
     },
-    "@azure/identity": "^4.13.1"
+    "@azure/identity": "^4.13.1",
+    "jest-runner-vscode": {
+      "@vscode/test-electron": "^3.1.0"
+    }
   },
   "lint-staged": {
     "./**/*.{json,css,scss}": [

extensions/ql-vscode/package.json

@@ -24,9 +24,9 @@ describe("launching with a minimal workspace", () => {
     const document = await workspace.openTextDocument(documentPath);
     expect(document.languageId).toEqual("ql");
     // Wait for the extension to activate, polling with a timeout.
-    await waitForActivation(ext!, 30_000);
+    await waitForActivation(ext!, 90_000);
     expect(ext!.isActive).toBeTruthy();
-  }, 60_000);
+  }, 120_000);
 
   async function waitForActivation(
     extension: Extension<any>,