[Bazel CI] Downstream project broken by rules_java upgrade

[meteorcloudy]

• rules_android: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/4122#0191e992-eae4-42e8-9a83-2c25041a8537
• rules_android_ndk: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/4122#0191e992-ef33-4327-b223-c143ed2eb0e9
• rules_testing: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/4122#0191e992-f0c9-4795-9cad-20f0c60aa06e

(04:10:49) ERROR: /var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/67c259e1fb9766950734b85418b03ced/external/rules_java_builtin/toolchains/BUILD:285:14: While resolving toolchains for target @@rules_java_builtin//toolchains:platformclasspath (4f6c53c): No matching toolchains found for types @@rules_java_builtin//toolchains:bootstrap_runtime_toolchain_type.
To debug, rerun with --toolchain_resolution_debug='@@rules_java_builtin//toolchains:bootstrap_runtime_toolchain_type'

Bisect points to https://github.com/bazelbuild/bazel/commit/f92124acf3d0eb99d06570ddc380aca7ab354b90

[meteorcloudy]

@hvadehra Looks like https://github.com/bazelbuild/bazel/pull/23571 is getting cherry-picked back to 7.4, you probably want to fix this one to make sure the upgrade is backwards compatible?

[meteorcloudy]

I bisected with rules_android using

bazel --bisect=c364bd65eee1b5b0874de85f41c39c2d6915ff8b..HEAD build --enable_workspace --noenable_bzlmod --nobuild //test/rules/...

[meteorcloudy]

https://github.com/kythe/kythe/issues/6138 might be the same issue

[hvadehra]

cc @comius

[hvadehra]

Looks like the failures are only when using WORKSPACE, and not with bzlmod. So presumably they're picking up an older version of rules_java?