Windows symlinked binaries are unreliable with remote cache enabled.

### What version of rules_go are you using?
* `0.47.1`
* But present in in `0.48.1` too.

### What version of gazelle are you using?

NA

### What version of Bazel are you using?

* `bazel 8.0.0-pre.20240607.2`

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

Yes.

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

Various but bug exists on Windows.

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

NA

### What did you do?

Run builds in CI which result in build failures on Windows as described in Same build failures as https://github.com/bazelbuild/bazel/issues/21747

### What did you expect to see?

No failures.

### What did you see instead?

Build failure due to a broken executable fetched from remote cache.

Start by reproducing the CI build on Windows with rules_go 0.47.1 or 0.48.1 and Bazel 8.0.0-pre.20240607.2, then compare the failure with Bazel issue 21747. Done means builds using remote cache no longer fetch a broken executable.

Written by the indexing model from the issue text.