…etries fresh names

The polling loop from #24469 waits for a stale same-name container to
disappear before docker run, but dockerd can still release the name a beat
after the container stops being inspectable. Wrap docker run in a bounded
retry that force-removes the name's holder on 'already in use' conflicts.

Also export a unique NAME_POSTFIX before the flake retry in run_test_cmd so
the retry's containers/compose projects never contend with the failed
attempt's teardown in the first place.

The #24469 inspect-poll waited up to 30s for a stale container's name to
free before docker run, but the retry loop now covers the same race
(including the window after the container stops being inspectable) while
actively force-removing the name's holder between attempts. Keep the
initial best-effort docker rm -f so the common stale-container case does
not burn a retry, and give the retry loop exponential backoff
(1+2+4+8+16s, ~30s total) to preserve the old tolerance window.

…-race-retry

#24547)

Stacked on #24477. Fixes the 49-per-run automine FLAKEs reported there
and on this PR's first run.

**Root cause** (`yarn-project/end-to-end/bootstrap.sh`): the `tests`
array listed the automine subdirectories explicitly and also kept the
`src/automine/!(simulation)/**/*.test.ts` catch-all (a merge artifact
from merging merge-train/fairies-v5 into
mv/e2e-onchain-delivery-harness), so every nested automine test was
emitted as two byte-identical cmds (268 jobs for 145 tests). Both copies
run under the same docker container name. When the two copies overlap in
time, the later one's docker_isolate force-removes the earlier one's
live container (or wins the name-conflict retry added in #24477), the
earlier test fails, and its automatic retry (which gets a fresh
`NAME_POSTFIX`) passes: a deterministic FLAKED-with-code-0 for every
overlapping pair, which is why the count sits near 49 on every run and
why only `src/automine/**` flakes. When the copies do not overlap, the
second is skipped by the test cache, hiding the duplication. The parent
branch's "docker container name conflicts" were the same duplication
seen from the other side.

- Remove the seven redundant per-directory globs; the deduplicated
unique cmd set is unchanged (verified byte-identical before/after, 145
automine jobs, zero duplicates in both `CI_FULL` modes).