Bazel remote execution fails to end early on first test failure, but exits early on local execution with `--notest_keep_going`

### Description of the bug:

```
(18:16:05) FAIL:
(18:23:00) [97,869 / 97,901] 1594 / 1671 tests, 1 failed; Testing
(18:27:48) [97,904 / 97,905] 1627 / 1671 tests, 1 failed; Testing
```
On remote execution

### Which category does this issue belong to?

Remote Execution

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

To repro,

have a test fail

bazel coverage //... --notest_keep_going

and remote execution with buildbarn will run all tests until failure

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

Linux

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

7.4.1

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

```

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

_No response_

Start by reproducing the failure with `bazel coverage //... --notest_keep_going` using remote execution with BuildBarn, then compare it with local execution on Linux. Done means remote execution stops running tests after the first failure, matching the local behavior.

Written by the indexing model from the issue text.