darwin-sandbox: Found unexpected entries in sandbox base

### Description of the bug:

Ran `bazel test //...` and met with following output at the end:
```
INFO: Found 18 targets and 4 test targets...
INFO: Elapsed time: 264.025s, Critical Path: 251.05s
INFO: 4621 processes: 1755 action cache hit, 53 internal, 4568 darwin-sandbox, 4 local.
INFO: Build completed successfully, 4621 total actions
//dynamodb:dynamodb_hygiene_test PASSED in 8.9s
//mysql:mysql_listening_on_port_hygiene_test PASSED in 3.1s
//mysql:mysql_listening_on_socket_hygiene_test PASSED in 3.1s
//redis:redis_hygiene_test PASSED in 1.4s

Executed 4 out of 4 tests: 4 tests pass.
There were tests whose specified size is too big. Use the --test_verbose_timeout_warnings command line option to see which ones these are.
FATAL: bazel crashed due to an internal error. Printing stack trace:
java.lang.IllegalStateException: Found unexpected entries in sandbox base. Please report this in https://github.com/bazelbuild/bazel/issues. The entries are: darwin-sa, _moved_trash_dir, sandbox_stash
at com.google.devtools.build.lib.sandbox.SandboxModule.checkSandboxBaseTopOnlyContainsPersistentDirs(SandboxModule.java:428)
at com.google.devtools.build.lib.sandbox.SandboxModule.afterCommand(SandboxModule.java:465)
at com.google.devtools.build.lib.runtime.BlazeRuntime.afterCommand(BlazeRuntime.java:776)
at com.google.devtools.build.lib.runtime.BlazeCommandDispatcher.execExclusively(BlazeCommandDispatcher.java:807)
at com.google.devtools.build.lib.runtime.BlazeCommandDispatcher.exec(BlazeCommandDispatcher.java:266)
at com.google.devtools.build.lib.server.GrpcServerImpl.executeCommand(GrpcServerImpl.java:608)
at com.google.devtools.build.lib.server.GrpcServerImpl.lambda$run$0(GrpcServerImpl.java:679)
at io.grpc.Context$1.run(Context.java:566)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)

INFO:
```

### Which category does this issue belong to?

_No response_

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

not sure, rerunning didn't exhibit it

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

darwin

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

release 9.0.0rc5

### 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` ?

```text
➜ examples git:(master) ✗ git remote get-url origin; git rev-parse HEAD
git@github.com:dzbarsky/rules_itest.git
289ddbd3dc29260ccab7ead3c034ace2b64a1208
```

### 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?

cc @fmeum :)