Pin test VS Code version to 1.130.0 to unbreak macOS CI

[sean-mcmanus]

Summary

The macOS CI legs are failing deterministically on every run because the integration tests download the newest stable VS Code (1.131.0, released today) and the installed @vscode/test-electron (^2.3.10) cannot launch its macOS arm64 bundle:

✔ Downloaded VS Code into .../vscode-darwin-arm64-1.131.0
✔ Validated version: 1.131.0
Test error: Error: spawn .../vscode-darwin-arm64-1.131.0/Visual Studio Code.app/Contents/MacOS/Electron ENOENT
Exit code: -2

The scenario tests resolve the test VS Code via downloadAndUnzipVSCode(options) with no pinned version, so they always pull latest stable — meaning a brand-new release can break CI for main and every open PR at once (Linux/Windows currently pass; only macOS is affected). This pins the downloaded test VS Code to 1.130.0 (the last release that launches under the current @vscode/test-electron) so CI is deterministic again.

Follow-up (separate change): bump @vscode/test-electron so newer stable releases launch, then the pin can be raised or removed.

This PR was created by Copilot with Claude Opus 4.8 (in VS Code). Any PR comments starting with Copilot says: are generated by Copilot.

[Copilot]

Pull request overview

Pins the VS Code version used by the extension’s integration/scenario test harness so macOS CI no longer breaks when a new stable VS Code release ships that the current @vscode/test-electron cannot launch on macOS arm64.

Changes:

• Introduces a testVSCodeVersion constant (1.130.0) to pin the downloaded VS Code build used for tests.
• Passes the pinned version into downloadAndUnzipVSCode via the exported options object.
• Adds inline comment context explaining the macOS arm64 failure mode and why the pin is necessary.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.