Bump dependency versions for rules_scala v7.1.2

[mbland]

Description

Updates the following dependencies:

• Go: 1.25.0 => 1.25.1
• bazel-contrib/.github:release_ruleset.yaml: 7.2.2 => 7.2.3
• bazel-contrib/publish-to-bcr:publish.yaml: 0.1.0 => 1.0.0
• golang.org/x/tools: 0.36.0 => 0.37.0
• google-common-protos: 2.61.0 => 2.61.1
• jline: 3.30.5 => 3.30.6
• protobuf-java: 4.32.0 => 4.32.1
• protobuf: 32.0 => 32.1
• rules_cc: 0.2.3 => 0.2.8
• rules_python: 1.6.0 => 1.6.1
• rules_shell: 0.6.0 => 0.6.1
• util-interface: 1.11.5 => 1.11.6

Also changes all the bazel_dep declarations for protobuf to remove the curently unnecessary version parameter from:

bazel_dep(
    name = "protobuf",
    version = "32.0",
    repo_name = "com_google_protobuf",
)

to:

bazel_dep(name = "protobuf", repo_name = "com_google_protobuf")

If protocolbuffers/protobuf#19679 ever lands, we'll remove the single_version_override statements and restore version to these bazel_dep declarations altogether and rely on deps/latest/MODULE.bazel.

Motivation

This is mostly a routine version bump before a new release.

The changes to the bazel_dep statements for protobuf aim to make the diffs smaller when increasing the protobuf version in the future.

[mbland]

@simuons @WojciechMazur Let me know if you're cool with releasing v7.1.2 after this lands. I don't mind if you merge it and release it, or if you'd prefer I do it. And if you prefer this be v7.2.0 instead, I'm happy to update it accordingly.

[WojciechMazur]

I'm fine with cutting of a new release, it would also be good to test out release procedure with the new maintenance role.

[mbland]

OK, I just finished running./test_all.sh with all the Bazel {7,8,rolling,last_green} and {Bzlmod, legacy WORKSPACE} combinations, and all is well. Merging, then pushing v7.1.2 to see what happens!

[simuons]

Hi, @mbland, glad to see that you have released a new version! Sorry for unresponsiveness.

[mbland]

@simuons No apologies necessary. 🙂