Add batch_commands to presubmit.yml (bazel-contrib#3389)

Fix bcr presubmit build on windows

(cherry picked from commit c181f93)

Add batch_commands to presubmit.yml (bazel-contrib#3389)

Fix bcr presubmit build on windows

(cherry picked from commit c181f93)

fix: make CI pass with the next version of Bazel (9.0.0rc1) (bazel-co…

…ntrib#3393)

Explicitly load CcToolchainConfigInfo in the fake cc toolchain config.

For examples/bzlmod, bump rules_rust to a newer version so that it pulls
in dependencies that work correctly with Bazel 9.0.0rc1.

Work towards bazel-contrib#3392

(cherry picked from commit 49b6630)

gazelle: set min rules_python version as 1.4 (bazel-contrib#3383)

rules_python 1.4 is when the python.defaults tag class was introduced,
which is used in the example's module file.

Fixes BCR presubmit failures in
bazelbuild/bazel-central-registry#6330 and
bazelbuild/bazel-central-registry#6241

(cherry picked from commit d08cf53)

build: change gazelle rules_python override to use bazelrc (bazel-con…

…trib#3382)

This is because the `--override_module` flag in BCR presubmit configs
can't affect local_path_override in MODULE.bazel.

Per
bazelbuild/bazel-central-registry#6241 (comment)

(cherry picked from commit caab0fa)

build: change gazelle rules_python override to use bazelrc (bazel-con…

…trib#3382)

This is because the `--override_module` flag in BCR presubmit configs
can't affect local_path_override in MODULE.bazel.

Per
bazelbuild/bazel-central-registry#6241 (comment)

(cherry picked from commit caab0fa)

Merge branch 'main' into release/1.7

chore: create_archive_and_notes.sh: correctly capture and check grep …

…result

bump to 1.6.3

(cherry picked from commit 7afced9)

fix(pypi): select the lowest available libc version by default (bazel…

…-contrib#3255)

The bazel-contrib#3058 PR has subtly changed the default behaviour of
`experimental_index_url` code path and I think in order to make things
easier by default for our users we should go back to that behaviour.

And in addition to this we are starting to make use of the Minimal
Version Selection algorithm for the platforms. This in general allows
users to configure the upper platform version for a particular wheel.
This meant that we had to change the semantics of the API a little:
1. Use MVS for each platform platform tag.
2. Make it such that earlier entries are overridden by later ones, i.e.
   `["musllinux_*_x86_64", "musllinux_1_2_x86_64"]` is effectively the
   same as just `["musllinux_1_2_x86_64"]`.

A remaining thing that will be left as a followup for bazel-contrib#2747 will be to
figure out how to allow users to ignore certain platform tags.

Fixes bazel-contrib#3250

---------

Co-authored-by: Richard Levasseur <[email protected]>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

Cherry-picked from 5fa1a87