Update Bazel's embedded JDK to 23

[fmeum]

In addition to performance improvements, this JDK release contains a fix for https://bugs.openjdk.org/browse/JDK-8330077, which allows --watchfs to handle a configurable number of changes to a watched path rather than maxing out at 500.

s390x and ppc64le can only be updated to 22, Windows arm64 can switch to Zulu JDK 21.

[fmeum]

cc @coeuvre as we talked about Loom performance testing with the most recent JDK used at Google

[fmeum]

@bazel-io fork 7.4.0

[meteorcloudy]

@fmeum Do you now how stable a new non-LTS JDK version usually is? I'm fine merging this at HEAD but do you see any risk of backporting it to 7.4.0?

[fmeum]

@meteorcloudy Non-LTS JDKs are generally as stable as LTS releases, they are just not maintained with patches for longer than 6 months. But I don't think we have cherry-picked JDK updates before anyway ;-)

That said, I have seen some commits to keep it up-to-date with the more recent JDK used internally for Blaze. We should also cherry-pick those if necessary. @cushon @coeuvre Do you happen to recall which changes have been necessary to keep running with the latest JDK?

[meteorcloudy]

There are already some failures in https://buildkite.com/bazel/bazel-bazel/builds/29313#019209b3-4de9-4d46-87ae-8f7a13a68db4 (Not sure why they are not caught in presubmit)

Server terminated abruptly (error code: 14, error message: 'Socket closed', log file: '/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/ec321eb2cc2d0f8f91b676b6d4c66c29/sandbox/linux-sandbox/8918/execroot/_main/_tmp/a3e8969f357bed22ac8b1eeab84a428c/root/0e49712d29d8b302bc0b6e65669ad849/server/jvm.out')

[meteorcloudy]

@fweikert looks like the presubmit skipped most of the tests: https://buildkite.com/bazel/google-bazel-presubmit/builds/83889, I think this is a known issue of bazel-diff? Can we add the repositories.bzl to some allow list to make sure all tests are triggered?

[fweikert]

bazelbuild/continuous-integration#2038