fix: reject on non-zero exit code regardless of stderr (Windows hang)

[avgon]

Summary

Fixes the intermittent test hang on windows-latest reported in #13273.

Root Cause

In runTerminalCommand.ts, the close handler only rejected the promise when both code !== 0 and stderr was non-empty:

s if (code !== 0 && stderr) { reject(...) }

On Windows, PowerShell's CommandNotFoundException can be flushed to stdout instead of stderr, or the stderr buffer may not be populated by the time the close event fires. When that happens the guard is false, the reject is skipped, and the promise is left permanently pending. The tool's own 180 s timeout (TIMEOUT_MS) cannot rescue it because vitest's 30 s testTimeout fires first.

Changes

1. Reject on any non-zero exit code regardless of stderr content. Falls back to stdout or a generic message for diagnostics when stderr is empty.
2. Add -NoProfile to the Windows PowerShell invocation to prevent slow/interfering profile scripts from delaying error output.

Testing

• The existing should handle non-existent commands test now exercises the corrected path: PowerShell exits with code 1 and the promise rejects immediately whether the error lands in stderr or stdout.
• All other tests in runTerminalCommand.test.ts are unaffected since successful commands still resolve normally.

Closes #13273

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[avgon]

I have read the CLA Document and I hereby sign the CLA