--experimental_remote_download_outputs breaks symlink outputs

[philwo]

Description of the problem / feature request:

When using --experimental_remote_download_outputs no matter whether =minimal or =toplevel, Bazel fails to build rules_go with these errors:

(13:01:33) ERROR: /workdir/tests/core/go_path/BUILD.bazel:5:2: output 'tests/core/go_path/link_path/pkg/linux_amd64/example.com/repo/cmd/bin.a' is a dangling symbolic link
(13:01:33) ERROR: /workdir/tests/core/go_path/BUILD.bazel:5:2: output 'tests/core/go_path/link_path/pkg/plan9_arm/example.com/repo/cmd/bin.a' is a dangling symbolic link
(13:01:33) ERROR: /workdir/tests/core/go_path/BUILD.bazel:5:2: output 'tests/core/go_path/link_path/pkg/linux_amd64/example.com/repo/pkg/lib.a' is a dangling symbolic link
(13:01:33) ERROR: /workdir/tests/core/go_path/BUILD.bazel:5:2: Couldn't build file tests/core/go_path/link_path/src/example.com/repo/cmd/bin/bin.go: not all outputs were created or valid

Failing build with the flag: https://buildkite.com/bazel-testing/rules-go-golang/builds/181
Working build without the flag: https://buildkite.com/bazel-testing/rules-go-golang/builds/182

What operating system are you running Bazel on?

Fails on Linux and macOS.

What's the output of bazel info release?

Bazel 0.26.1

[philwo]

@buchgr Friendly ping. This is blocking the „remote builds without bytes“ rollout on CI.

[coeuvre]

Is this still an issue today?

[tjgq]

I ran the downstream pipeline with --remote_download_minimal (which includes an RBE build of rules_go) and there were no failures, so I'll consider this one fixed.