Merge release commits to 29.x

…#19434)

This reverts commit 471ff77.

The default name for the rules_jvm_external.maven rule is "maven". When not set, it defaults to "maven". For root modules also using rules_jvm_external, the name clash causes a warning:

```
DEBUG: $TMP/external/rules_jvm_external~/private/extensions/maven.bzl:154:14:
The maven repository 'maven' is used in two different bazel modules,
originally in '<my_workspace>' and now in 'protobuf'
```

Summarizing @shs96c in [1]:

> The common maven repo name allows rulesets to contribute to the user's JARs.
> However, this implies that maven is for the end user, not for transitive
> dependencies. If a ruleset needs private dependencies, it should use a custom
> namespace rather than the maven namespace.

Since protobuf is not contributing to user's JARs, we'll use a custom namespace. There's precedent for using a custom namespace for library modules:

- rules_jvm_external uses `rules_jvm_external_deps` instead of `maven`.
- rules_kotlin uses `kotlin_rules_maven` instead of `maven`.

[1]: bazel-contrib/rules_jvm_external#916 (comment)

Fixes #16839.

Closes #18641

COPYBARA_INTEGRATE_REVIEW=#18641 from jschaf:joe/protobuf-maven bd2c62f
PiperOrigin-RevId: 684625084

Co-authored-by: Joe Schafer <joe.schafer@delta46.us>

Merge release commits to 29.x

This should fix some Windows tests that are failing to install a
downgraded CMake version.

I also fixed some of the Bazel examples tests. Two of the test runs
seemed to be omitting a Bazel version and were inadvertently using Bazel
8.

Fixes #19671

PiperOrigin-RevId: 706729524

PiperOrigin-RevId: 705148623

Co-authored-by: Mike Kruskal <mkruskal@google.com>

PiperOrigin-RevId: 706827598

Co-authored-by: Protobuf Team Bot <protobuf-github-bot@google.com>