[CI] Bump Bazel version to 4.2.2

[shrekris-anyscale]

Why are these changes needed?

A compatibility issue between Bazel, Protoc, and MacOS Monterey is solved starting in Bazel 4.2.2. This change upgrades the Bazel version from 4.2.1 to 4.2.2.

Related issue number

Closes #24241.

Checks

• I've run scripts/format.sh to lint the changes in this PR.
• I've included any doc changes needed for https://docs.ray.io/en/master/.
• I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
• Testing Strategy
  • Unit tests
  • Release tests
  • This PR is not tested :(

[jjyao]

Could you also double check if there is any public doc that references 4.2.1?

[shrekris-anyscale]

It looks like the Windows tests are failing. I'll investigate further, but there's a chance that Windows should continue using Bazel 4.2.1.

Depending on that, we may/may not want to change this line and this line in the docs.

[shrekris-anyscale]

Could you also double check if there is any public doc that references 4.2.1?

@jjyao Good idea! I didn't notice any public doc that references 4.2.1 other than the lines about Windows I mentioned here.

[shrekris-anyscale]

I made a PR in the buildkite-ci-stack repo to upgrade the Windows' CI Bazel version to 4.2.2. I also updated the references in the Windows docs to refer to Bazel 4.2.2 instead of 4.2.1.

Once the buildkite-ci-stack PR is merged, the Windows tests on this PR should pass.

[shrekris-anyscale]

As a status update– we ran the packer command to update Bazel for Windows. However, the packer script ran into some issues:

==> amazon-ebs.ci-windows: The command 'powershell -Command $ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue'; ./main.ps1' returned a non-zero code: 1

See here for full command output.

Once this issue is resolved, we can finish the Windows Bazel update and then merge in this change.

[pdames]

+1 to getting this PR finalized and merged ASAP. I just went through the same discovery and troubleshooting process on MacOS Monterey and was about to submit the same PR before finding this one.