chore: prepare CHANGELOG for 0.38.0 release (bazel-contrib#2384)

fix(bzlmod): generate config_setting values for all python toolchains (…

…bazel-contrib#2350)

PR bazel-contrib#2253 broke how the config settings are generated and only generated the
config
setting values for the python version values that we would have the
registered
toolchains for. This PR restores the previous behaviour. However, if the
root
module uses `python.override` to remove the allowed toolchains, then
`config_settings` will be also affected.

(cherry picked from commit 9340a81)

Conflicts:
- CHANGELOG.md

docs: update changelog for 0.37.1 (bazel-contrib#2330)

Update the headers and sections for the 0.37.1 release.

chore: update changelog for 0.37.0 (bazel-contrib#2311)

Update the changelog for 0.37.0

---------

Co-authored-by: Ignas Anikevicius <240938+aignas@users.noreply.github.com>

chore: prepare 0.36.0 release (bazel-contrib#2245)

Prep for 0.36.0 release (can be tagged after this PR is merged).

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)