Exclude .vscode-test from vitest and align the workflows

[beumerr]

The v0.3.0 publish run failed at Package VSIX. Nothing shipped — the Marketplace and Open VSX steps were skipped.

What happened

Error: No test suite found in file .vscode-test/vscode-linux-x64-1.133.0/resources/app/
extensions/markdown-language-features/scripts/updateMarkdownEditorPackageJson.test.mts

Test Files  1 failed | 14 passed (15)
Tests       359 passed (359)

Every one of our 359 tests passed. The failure was a 15th test file that isn't ours — one VS Code ships inside itself.

The chain:

1. Steps 11–12 run the E2E suites, which download VS Code into .vscode-test/.
2. Step 13 runs vsce package, which triggers vscode:prepublish → npm run test:unit again.
3. That second vitest run globs the freshly-downloaded VS Code tree and collects updateMarkdownEditorPackageJson.test.mts, which has no suite in it.

Note step 10 — the first test:unit — passed. It ran before the download.

The fix

.vscode-test/** added to vitest's exclude. This also bites anyone running npm test locally after npm run test:vscode.

Why CI was green

The two workflows had drifted, in three ways:

	ci.yml	publish.yml
typecheck	yes	no
Packages the VSIX	no	yes
E2E and test:unit share a workspace	no — separate jobs, separate runners	yes — one job, sequential

That last row is the whole reason this was invisible. In CI, .vscode-test/ never exists on the same runner as test:unit, so the collision cannot occur. In publish, it always does.

So both are brought back in line:

• publish.yml gains the missing typecheck.
• ci.yml packages the VSIX at the end of the E2E job — deliberately after the download has populated .vscode-test/, mirroring publish's ordering. That exercises vscode:prepublish on every PR and reproduces this class of failure before a release, not during one.

Verification

Planted the offending file locally at the same path:

• before the fix: Test Files 1 failed | 14 passed (15) — matches CI exactly
• after the fix: Test Files 14 passed (14)

vsce package also confirmed working locally (26 files, 977.88 KB).