Bazel downstream projects are broken due to out-dated rules_java version with Bazel@HEAD

[meteorcloudy]

Context

In #18373, we agreed on using rule sets as the source of truth to load toolchains and required dependencies for specific languages (e.g. rules_java, rules_cc). This reduces the duplicated information in Bazel's default @bazel_tools repo and fits our long term goal to make Bazel language-agnostic.

975866a implemented that for rules_java. Unfortunately, this is a breaking change because Bazel now relies on a compatible rules_java version to be defined.

• When using Bzlmod, this is no problem, because the default bazel_tools module specify a new rules_java version, and thanks to minimal version resolution, we'll always get a compatible rules_java version.
• When using WORKSPACE, Bazel append a WORKSPACE suffix which defines the compatible rules_java version, however, it could be overridden by user's WORKSPACE content.

Related:

• Sync java_tools, remote JDKs, and java toolchains in rules_java with Bazel HEAD rules_java#110
• Respect rules_java as the source of truth for java toolchains #18423

Broken projects

https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/3066

Potential Solutions

• Upgrade projects to use newer rules_java. There are too many projects to fix and this is probably not a one-time effort since rules_java is coupled with Bazel's builtin starlarkified java rules.
• Rename the embedded rules_java in WORKSPACE suffix to rules_java_builtin.

[meteorcloudy]

I couldn't find any easy fix for this issue, so rolling back the breaking change for now.

[meteorcloudy]

Introducing rules_java_builtin seems to work, working on a fix now.