[CI Failure] Flaky: VS Code extension E2E (Windows, apphost-tree) shard fails with generic exit code 1, unrelated to PR changes

## Build Information

Build: https://github.com/microsoft/aspire/actions/runs/32205890727
Build error leg: Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, apphost-tree)
Pull request: #19474

## Error Message

```
Process completed with exit code 1. (Run extension E2E tests step failed; job logs unavailable: 'Failed to fetch logs for job'). No TRX test failures extracted. Occurs on 'VS Code extension E2E (Windows, apphost-tree)' shard.
```

## Description

Flaky: VS Code extension E2E (Windows, apphost-tree) shard fails with generic exit code 1, unrelated to PR changes

**Type**: flaky-test

## Occurrences

| Date | Build | Job | PR |
|------|-------|-----|----|
| 2026-08-19 | [32205890727](https://github.com/microsoft/aspire/actions/runs/32205890727) | Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, apphost-tree) | #19474 |
| 2026-09-01 | [33564722037](https://github.com/microsoft/aspire/actions/runs/33564722037) | Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, apphost-tree) | #19832 |
| 2026-09-04 | [33879357897](https://github.com/microsoft/aspire/actions/runs/33879357897) | Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, dynamic-debug-configuration) | #19929 |
| 2026-09-10 | [34426557203](https://github.com/microsoft/aspire/actions/runs/34426557203) | Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, apphost-tree) | #19653 |
| 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 |

Start by inspecting the linked GitHub Actions runs and the Tests / Run VS Code extension E2E tests job for the Windows apphost-tree shard. Compare the listed Windows failures, including dynamic-debug-configuration and unit tests, to determine whether they share a cause. Done means the flaky failure has an actionable root cause and the affected test or workflow is made reliable.

Written by the indexing model from the issue text.