chore: update changelog for 0.35.0 release (bazel-contrib#2124)

Updates the changelog to have 0.35.0 headers in prep for release

(chore): Remove the extra indirection and `bzlmod` folder (bazel-cont…

…rib#2022)

The `bzlmod` folder seems like unnecessary indirection now. It was
perhaps useful as we developed bzlmod support, but we no longer need it
and it makes navigating the repository more difficult.

fix(toolchain): disable exec toolchain by default (bazel-contrib#1968)

This makes the exec tools toolchain disabled by default to prevent
toolchain resolution
from matching it and inadvertently pulling in a dependency on the
hermetic runtimes.
While the hermetic runtime wouldn't actually be used (precompiling is
disabled
by default), the dependency triggered downloading of the runtimes, which
breaks
environments which forbid remote downloads they haven't vetted (such a
case is
Bazel's own build process).

To fix this, a flag is added to control if the exec tools toolchain is
enabled or not.
When disabled (the default), the toolchain won't match, and the remote
dependency isn't
triggered.

Fixes bazel-contrib#1967.

Cherry-pick of cf1f36d.

---------

Co-authored-by: Richard Levasseur <rlevasseur@google.com>

fix(rules): drop the unused argument (bazel-contrib#1953)

It seems that there is an extra argument that is there but I am not sure
about
the reason, it is most likely a leftover. As part of this change we add
an
analysis test for non-windows zip building. I could reproduce the
failure and
now the newly added test passes.

Fixes bazel-contrib#1954

chore: changelog changes for release 0.33.0 (bazel-contrib#1950)

fix(toolchain): delete 'share/terminfo' for recent linux python toolc…

…hains (bazel-contrib#1898)

This affects Linux toolchains that have the `terminfo` databases bundled
with the toolchain. Our solution to this is to remove the
`share/terminfo` altogether if we are downloading an affected `linux`
toolchain.

Tested with (on a Mac):
```console
bazel build --platforms=//tests/support:linux_x86_64 @python_3_11//:files
bazel build --platforms=//tests/support:windows_x86_64 @python_3_11//:files
```

Workaround
astral-sh/python-build-standalone#231
Fixes bazel-contrib#1800

fix(bcr): add mandatory gazelle bcr presubmit attrs (bazel-contrib#1894)

The same as in f1d1732.

Fixes that were needed in
[bazel/bazel-central-registry#2019](bazelbuild/bazel-central-registry#2019).

chore: release notes for 0.32.0 (bazel-contrib#1893)

Updates release notes for 0.32.0

chore: Update changelog for 0.31.0 (bazel-contrib#1754)

* Create 0.31.0 section
* Move pystar note out of 0.30.0 section and into 0.31.0

tests(bcr): Set Bazel version in BCR presubmit config. (bazel-contrib…

…#1753)

BCR now requires the presubmit configs to specify the Bazel versions to
run tests with. Without this, the BCR checks fail and we can't do
releases to BCR.