fix(e2e): stabilize flaky provider suite ordering and zai requestCapture race

[roomote]

Opened on behalf of Elliott de Launay. View the task or mention @roomote for follow-up asks.

What problem this solves

Fixes two intermittent e2e flakes observed together in CI:

• [BUG] e2e: Bedrock test leaves code mode pinned to bedrock provider, causing Terminal Profile and execute_command suites to timeout #512 — Bedrock suite left code mode pinned to the Bedrock provider when Mocha's non-deterministic glob happened to load providers/bedrock.test.ts before the tool suites. Tool suite tasks started in code mode then hit the Bedrock endpoint, got 404 No fixture matched, and timed out after 60–90 s each.
• [BUG] e2e: Z.ai glm-5-turbo max_tokens assertion flaky due to shared requestCapture object #514 — Z.ai suite shared a single requestCapture object across tests. A straggling async API call from the glm-5.1 test could overwrite requestCapture.maxTokens after the glm-5-turbo test's setup() reset it but before its own request landed, causing the 40_551 assertion to read 40000 instead.

Why this change was made

Both failures were timing/ordering-dependent — they passed on re-run with a different file order or timing. Rather than rely on luck, the fixes make the suite order deterministic and the assertion immune to async stragglers.

Changes

• apps/vscode-e2e/src/suite/index.ts — sort test files so providers/ suites always run after all other suites (alphabetical within each bucket). Provider teardown state can no longer bleed into tool suites regardless of glob order.
• apps/vscode-e2e/src/suite/providers/zai.test.ts — snapshot requestCapture.maxTokens immediately after waitUntilCompleted returns in both glm-5.1 and glm-5-turbo tests, before any straggling async calls can overwrite it.

User impact

No production code changed. CI e2e-mock job should no longer flake on these two failure modes.

Closes #512
Closes #514

[roomote]

2 issues outstanding. Action required. See task

• platform-unit-test (windows-latest) is still pending after the 10-minute review wait window. — dismissed: superseded by a fresh CI run for the latest commit.
• Moving the draft-state triggers onto pull_request lets the PR branch redefine the approval gate and bypass the two-human-approval requirement.
• platform-unit-test (windows-latest) is still pending after the 10-minute review wait window. — dismissed: the latest PR head completed this job successfully.
• platform-unit-test (ubuntu-latest) is still pending after the 10-minute review wait window.
• platform-unit-test (windows-latest) is still pending after the 10-minute review wait window.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[edelauna]

🤖