Build ID: revisit #1732

To solve https://github.com/bazel-contrib/rules_go/issues/1693, `rules_go` has been overriding build IDs with a static string, however this can be problematic in some circumstances (e.g. macOS unified logging).

Seems like `darwin/arm` has not been supported since go `1.15`: is there still any reason to keep https://github.com/bazel-contrib/rules_go/pull/1732 in? If so, how about at least making it optional/configurable?

Start by reading issues #1693 and #1732 and the pull request linked from the issue to understand the static build ID override and the darwin/arm support history. Inspect the current rules_go implementation that applies the override; done means determining whether it is still needed and, if retained, defining and documenting a configurable behavior.

Written by the indexing model from the issue text.