[CI Failure] Flaky: DashboardClientTests.WatchWithRecovery_RepeatedFailures_FiresMultipleDisconnectedEvents times out waiting for disconnected events

## Build Information

Build: https://github.com/microsoft/aspire/actions/runs/31742946349
Build error leg or test failing: Tests / Dashboard / Dashboard (ubuntu-latest) / `Aspire.Dashboard.Tests.Model.DashboardClientTests.WatchWithRecovery_RepeatedFailures_FiresMultipleDisconnectedEvents`
Pull request: #19345

## Error Message

```
System.TimeoutException : The operation at /_/tests/Aspire.Dashboard.Tests/Model/DashboardClientTests.cs:361 timed out after reaching the limit of 30000ms.
at Microsoft.AspNetCore.InternalTesting.AsyncTestHelpers.TimeoutAfter(Task task, TimeSpan timeout, String filePath, Int32 lineNumber)
at Aspire.Dashboard.Tests.Model.DashboardClientTests.WatchWithRecovery_RepeatedFailures_FiresMultipleDisconnectedEvents()
```

## Description

Flaky: DashboardClientTests.WatchWithRecovery_RepeatedFailures_FiresMultipleDisconnectedEvents times out waiting for disconnected events

**Type**: flaky-test

## Occurrences

| Date | Build | Job | PR |
|------|-------|-----|----|
| 2026-08-13 | [31742946349](https://github.com/microsoft/aspire/actions/runs/31742946349) | Tests / Dashboard / Dashboard (ubuntu-latest) | #19345 |

Start in tests/Aspire.Dashboard.Tests/Model/DashboardClientTests.cs at line 361 and inspect DashboardClientTests.WatchWithRecovery_RepeatedFailures_FiresMultipleDisconnectedEvents. Run the Dashboard test to reproduce the timeout and trace why the expected disconnected events are not observed. Done means the test reliably completes and verifies multiple disconnected events without timing out.

Written by the indexing model from the issue text.