fix: outdated sample versions

[rzhao271]

No description provided.

[rzhao271]

@copilot Check what runTests does and why it is unable to close VS Code or the unresponsive extension host after.

[Copilot]

@copilot Check what runTests does and why it is unable to close VS Code or the unresponsive extension host after.

runTests (in lib/runTest.ts) just spawns VS Code and waits for that process to emit exit/close. It only actively closes VS Code when the parent process receives SIGINT (Ctrl+C): first Ctrl+C sends SIGINT to VS Code, second Ctrl+C force-kills the process tree. If VS Code/extension host becomes unresponsive on its own, there is no built-in timeout/watchdog in runTests, so the promise can hang waiting for process exit.