[CI Failure] Flaky: ConformanceTests.TracingEnablesTheRightActivitySource_Keyed remote executor hangs due to Azure Identity credential failures on Windows runner

## Build Information

Build: https://github.com/microsoft/aspire/actions/runs/30416905407
Build error leg or test failing: Tests / Hosting.Testing / Hosting.Testing (windows-latest) / `Aspire.Azure.AI.OpenAI.Tests.ConformanceTests.TracingEnablesTheRightActivitySource_Keyed`
Pull request: #18561

## Error Message

```
Microsoft.DotNet.RemoteExecutor.RemoteExecutionException : Half-way through waiting for remote process.
at Microsoft.DotNet.RemoteExecutor.RemoteInvokeHandle.Dispose(Boolean disposing)
at Aspire.Azure.AI.OpenAI.Tests.ConformanceTests.TracingEnablesTheRightActivitySource_Keyed()
Caused by: Azure.Identity.CredentialUnavailableException: DefaultAzureCredential failed to retrieve a token - AzureCliCredential authentication failed: Azure CLI authentication timed out. AzurePowerShellCredential authentication failed: Azure PowerShell authentication timed out.
```

## Description

Flaky: ConformanceTests.TracingEnablesTheRightActivitySource_Keyed remote executor hangs due to Azure Identity credential failures on Windows runner

**Type**: flaky-test

## Occurrences

| Date | Build | Job | PR |
|------|-------|-----|----|
| 2026-07-29 | [30416905407](https://github.com/microsoft/aspire/actions/runs/30416905407) | Tests / Hosting.Testing / Hosting.Testing (windows-latest) | #18561 |

Start with Aspire.Azure.AI.OpenAI.Tests.ConformanceTests.TracingEnablesTheRightActivitySource_Keyed and the reported Windows runner build. Reproduce or inspect the remote executor wait alongside the Azure.Identity credential errors and authentication timeouts. Done means the conformance test completes reliably on windows-latest without hanging when Azure CLI or PowerShell credentials are unavailable.

Written by the indexing model from the issue text.