Update changelog for 0.25.0 (bazel-contrib#1389)

This is to prepare for the 0.25.0 release.

cleanup(tests): Use new APIs in rules_testing 0.4.0 (bazel-contrib#1307)

* Use public APIs for DictSubject and StrSubject.
* Use rules_testing's StructSubject instead of our own.

Work towards 1297

fix(bzlmod+gazelle): update BCR release presubmit to use correct exam…

…ple (bazel-contrib#1264)

The bzlmod-compatible build_file_generation example was moved to the
bzlmod_build_file_generation example.

This should fix the automatic build/release of the gazelle BCR module.

feat(bzlmod): Register a default toolchain (bazel-contrib#1259)

This makes rules_python always provide a default toolchain when using
bzlmod.

Note that, unlike workspace builds, the default is not the local
system Python (`@bazel_tools//tools/python:autodetecting_toolchain`).

Instead, the default is a hermetic runtime, but no guarantees are made
about the particular version used. In practice, it will be the latest
available Python version.

Work towards bazel-contrib#1233

feat(bzlmod): support entry_point macro (bazel-contrib#1220)

Add `entry_point` macro to the repo generated by the `pip.parse`
extension.
This works by using the canonical label literal, so should work without
users
needing to add the spoke repos to the `use_repo` statement. We test this
by
having an extra folder in the `bzlmod` example.

Fixes bazel-contrib#958.

feat: Support specifying multiple download URLs in tool_versions. (ba…

…zel-contrib#1145)

The interface of `repository_ctx.download` and
`repository_ctx.download_and_extract` supports string lists as well as
strings as the value of the `url` argument. This is the ultimate
destination of the `url` attribute in the `tool_versions` dictionary, so
it makes sense for it to support lists as well.

It is often useful to provide multiple download URLs, e.g. when
vendoring deps through a mirror (to guard against issues like [git
archive checksums
changing](https://github.blog/changelog/2023-01-30-git-archive-checksums-may-change/)
while still keeping the canonical download URL) or in an airgapped
setting (to support internal URLs alongside external URLs). This is also
pretty common around Bazel repository rules that download things, e.g.
[http_archive](https://bazel.build/rules/lib/repo/http#http_archive-urls),
so it can be expected to work with `tool_versions` too.

fix: Include filename when parsing imports for gazelle (bazel-contrib…

…#1133)

test(core): Add analysis tests for base Python rules. (bazel-contrib#…

…1102)

This is to provide some regression tests for the Starlark rewrite.

These tests are approximately the same as Bazel's Java-implemented
tests.

Work towards bazel-contrib#1069

Only set `py_runtime.coverage_tool` for Bazel 6 and higher. (bazel-co…

…ntrib#1061)

Only set `py_runtime.coverage_tool` for Bazel 6 and higher.

Avoid setting it in earlier version by checking `native.bazel_version`
in the repository rule and disabling it if less than Bazel 6 is
detected. A warning is also printed if coverage was requested, but
the Bazel version check is ignoring it.

Fixes bazel-contrib#1056

fix(release): wrong replacement for $(location) during code review (b…

…azel-contrib#1051)