bazelbuild
Only use workaround for darwin deadlock on darwin
What type of PR is this? Bug fix
What does this PR do? Why is it needed? Only use the workaround from https://github.com/bazelbuild/rules_go/pull/3536 on darwin.
(The lack of parallelism here makes this step heavy in the critical path for some of our builds.)
As this is only used for certain special binaries that are typically built very early in a build, I am slightly surprised to see this contribute to your critical path. Are you able to share a profile (--profile) that we can use to understand this better?
Generally speaking, an action should really only use up a single CPU core, so this setting is correct on all platforms. But of course we don't want it to negatively affect performance.
