- Fix Bazel@HEAD to the bazel version at time of branch cut
 - Use Bazel 7.3.2 for Bazel 7.x

See #230

PiperOrigin-RevId: 683574444
Change-Id: I4d1fe8e90392c37cc873ad97f079c9f3d9b401d5 (cherry picked from
commit 071069d)

Starlark implementation makes it possible to use the provider without
enabling `--experimental_google_legacy_api`.

Tested:  protocolbuffers/protobuf#18861

Copybara Import from #246

BEGIN_PUBLIC
Revert `bootstrap_runtime_toolchain_type` changes (#246)

This reverts the relevant bits from
bcc5062 and 30ecf3f. The minimum
supported Bazel version is now 6.4.0 which includes the type in
`@bazel_tools`.

Closes #246
END_PUBLIC


COPYBARA_INTEGRATE_REVIEW=#246
from bazelbuild:hvd_tests_for_bootclasspath
b666dc2 PiperOrigin-RevId: 702260069
Change-Id: Ie64994873a7b5609d4fb8b12a2472c82eb71493b

(cherry picked from commit 4206c53)

Conflicts:
  .bazelci/presubmit.yml
  MODULE.bazel
  test/repo/WORKSPACE

This should make it possible to pin `@rules_java` to `7.x` with Bazel 8
in projects that don't actually require/use `@rules_java`.

Otherwise, the `register_toolchains()` call in `MODULE.bazel` fails with
Bazel 8 due to `native.java_proto_library` and
`native.java_lite_proto_library` in `defs.bzl`

We can't build `@rules_java` `7.x` with Bazel 8 since `native.java_*`
are all gone

This is a cherry-pick of #258 into 7.x.

A new release would be appreciated as building bazel 7.x on riscv64
would require this.

---------

Co-authored-by: Jack Wolfard <31635014+JackWolfard@users.noreply.github.com>