go_cover cannot be used in the remote execution

### What version of rules_go are you using?

v0.43.0

### What version of gazelle are you using?

v0.34.0

### What version of Bazel are you using?

v6.4.0

### Does this issue reproduce with the latest releases of all the above?

if you run tidb tests like this with the remote execution.

```
make failpoint-enable
bazel run //:gazelle
bazel coverage --config=ci --strategy=CoverageReport=local --build_tests_only --nocache_test_results --test_keep_going=false --instrument_test_targets --@io_bazel_rules_go//go/config:cover_format=go_cover --//build:with_rbe_flag=true --experimental_split_coverage_postprocessing --experimental_fetch_all_coverage_outputs --define gotags=deadlock,intest -- //... -//cmd/... -//tests/graceshutdown/... -//tests/globalkilltest/... -//tests/readonlytest/... -//br/pkg/task:task_test -//tests/realtikvtest/...
```

### What operating system and processor architecture are you using?

### Any other potentially useful information about your toolchain?

### What did you do?

### What did you expect to see?

but you remove go_cover

you can get the coverage data.

### What did you see instead?

you will get empty coverage file.

Start by reproducing the reported Bazel coverage command for rules_go v0.43.0 with remote execution and the go_cover setting. Compare the generated coverage output with and without go_cover; the issue is done when remote execution produces a non-empty coverage file.

Written by the indexing model from the issue text.