Usage of `--experimental_remote_cache_eviction_retries` doesn't output gRPC or execution log for the first invocation

### Description of the bug:

There doesn't seem to be a way to debug `--experimental_remote_cache_eviction_retries` by producing gRPC or execution logs. This is because the second invocation on retry, will override the artifact produced by the first invocation.

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

Run an invocation by passing `--experimental_remote_grpc_log` or `--execution_log_binary_file` and see that the artifacts produced by the first invocation when there's a remote cache eviction are overwritten by the second invocation. This makes it impossible to debug the first invocation which failed if necessary.

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

macOS

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

6.2.0 @ 286306e

### 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 master; git rev-parse HEAD` ?

_No response_

### Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.

_No response_

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

_No response_

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

_No response_