[CI Failure] Flaky: VS Code extension unit tests job fails intermittently on Windows with generic exit code 1 and no retrievable logs

## Build Information

Build: https://github.com/microsoft/aspire/actions/runs/31556011348
Build error leg: Tests / Run VS Code extension unit tests (Windows)
Pull request: #19232

## Error Message

```
Process completed with exit code 1. (Job logs unavailable: 'Failed to fetch logs for job'). No TRX test failures extracted. Occurs on the 'Run VS Code extension unit tests (Windows)' job unrelated to PR changes touching only Aspire.Cli DotNet path resolution code.
```

## Description

Flaky: VS Code extension unit tests job fails intermittently on Windows with generic exit code 1 and no retrievable logs

**Type**: flaky-test

## Occurrences

| Date | Build | Job | PR |
|------|-------|-----|----|
| 2026-08-12 | [31556011348](https://github.com/microsoft/aspire/actions/runs/31556011348) | Tests / Run VS Code extension unit tests (Windows) | #19232 |
| 2026-09-11 | [34564571207](https://github.com/microsoft/aspire/actions/runs/34564571207) | Tests / Run VS Code extension unit tests (Windows) / Run VS Code extension unit tests (Windows) | #20057 |
| 2026-09-14 | [34858055930](https://github.com/microsoft/aspire/actions/runs/34858055930) | Tests / Run VS Code extension unit tests (Windows) / Run VS Code extension unit tests (Windows) | #19996 |

Start by inspecting the linked Actions runs and the “Run VS Code extension unit tests (Windows)” job configuration, then reproduce or rerun the Windows job to determine why it exits with code 1 without retrievable logs. Done means the intermittent failure has a documented cause and the job completes reliably with useful logs or test failure output.

Written by the indexing model from the issue text.