Bazel Mnemonic for exclusive tests can be improved

### Description of the bug:

when running bazel test //... on a directory of exclusive tests, you see the case of

Testing ..... 100 seconds

if there are multiple exclusive tests with long durations, i.e simulate with `sleep`, you'll have mnemonics saying testing when in reality the test isn't actually running yet, waiting for mnemonics

### Which category does this issue belong to?

Local Execution

### What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

create a bunch of exclusive tests with long timeouts

Use the following config for bazelrc

```
common --show_timestamps --curses=no --color=yes --announce_rc
build --progress_report_interval=10
```

### Which operating system are you running Bazel on?

ubuntu 20.04

### What is the output of `bazel info release`?

6.5.0

### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.

_No response_

### What's the output of `git remote get-url origin; git rev-parse HEAD` ?

_No response_

### If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.

_No response_

### Have you found anything relevant by searching the web?

_No response_

### Any other information, logs, or outputs that you want to share?

```
(01:53:58) [355 / 397] 134 / 150 tests; Testing //blah; 908s remote-cache ... (16 actions, 9 running)
```

Start by reproducing the report with multiple exclusive tests that use long sleeps, the supplied bazelrc settings, Ubuntu 20.04, and Bazel 6.5.0. Trace how progress messages label queued versus running exclusive tests; done means waiting tests are no longer reported as actively testing, while genuinely running tests retain accurate status.

Written by the indexing model from the issue text.