out of date bazel-toolchains warning

This is about rules_go's build itself, not the use of rules_go

### What version of rules_go are you using?

master ba7bdfd6b5118d135ae3f7984c94103510bf4167

### What version of gazelle are you using?

n/a

### What version of Bazel are you using?

4.2.2

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

Yes

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

macos 12.1 intel

### What did you do?

Running any bazel command in the rules_go repo gets you a lot of warning text and it takes up a lot of space when doing simple things.

### What did you expect to see?

```
$ bazel query '@bazel_tools//third_party/py/concurrent/...'
@bazel_tools//third_party/py/concurrent:srcs
@bazel_tools//third_party/py/concurrent:futures
```

### What did you see instead?

For example:

```
$ bazel query '@bazel_tools//third_party/py/concurrent/...'
DEBUG: /private/var/tmp/_bazel_jmhodges/3d68d33e850dbf6fe19f5c927ef82602/external/bazel_toolchains/rules/rbe_repo/version_check.bzl:68:14:
Current running Bazel is ahead of bazel-toolchains repo. Please update your pin to bazel-toolchains repo in your WORKSPACE file.
DEBUG: /private/var/tmp/_bazel_jmhodges/3d68d33e850dbf6fe19f5c927ef82602/external/bazel_toolchains/rules/rbe_repo/check
ed_in.bzl:125:14: buildkite_config not using checked in configs; Bazel version 4.2.2 was picked/selected but no checked in
config was found in map {"0.20.0": ["8.0.0"], "0.21.0": ["8.0.0"], "0.22.0": ["8.0.0", "9.0.0"], "0.23.0": ["8.0.0", "9.0.0"],
"0.23.1": ["8.0.0", "9.0.0"], "0.23.2": ["9.0.0"], "0.24.0": ["9.0.0"], "0.24.1": ["9.0.0"], "0.25.0": ["9.0.0"], "0.25.1": ["9.0.0"],
"0.25.2": ["9.0.0"], "0.26.0": ["9.0.0"], "0.26.1": ["9.0.0"], "0.27.0": ["9.0.0"], "0.27.1": ["9.0.0"], "0.28.0": ["9.0.0"],
"0.28.1": ["9.0.0"], "0.29.0": ["9.0.0"], "0.29.1": ["9.0.0", "10.0.0"], "1.0.0": ["9.0.0", "10.0.0"], "1.0.1": ["10.0.0"], "1.1.0":
["10.0.0"], "1.2.0": ["10.0.0"], "1.2.1": ["10.0.0"], "2.0.0": ["10.0.0"], "2.1.0": ["10.0.0"], "2.1.1": ["10.0.0", "11.0.0"], "2.2.0":
["11.0.0"], "3.0.0": ["11.0.0"], "3.1.0": ["11.0.0"], "3.2.0": ["11.0.0"], "3.3.0": ["11.0.0"], "3.3.1": ["11.0.0"], "3.4.1": ["11.0.0"],
"3.5.0": ["11.0.0"], "3.5.1": ["11.0.0"], "3.6.0": ["11.0.0"], "3.7.0": ["11.0.0"], "3.7.1": ["11.0.0"], "3.7.2": ["11.0.0"], "4.0.0":
["11.0.0"]}
@bazel_tools//third_party/py/concurrent:srcs
@bazel_tools//third_party/py/concurrent:futures
```

Reproduce the warnings with the Bazel command shown in the rules_go repository, then inspect the referenced external files rules/rbe_repo/version_check.bzl and rules/rbe_repo/checked_in.bzl. Determine why Bazel 4.2.2 is treated as ahead of the pinned bazel-toolchains data; done means routine commands retain their expected query output without the excessive outdated-toolchain warnings.

Written by the indexing model from the issue text.