Rebuild for libabseil 20250512, libgrpc 1.73 & libprotobuf 6.31.1

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update absl_grpc_proto_25q2.

Notes and instructions for merging this PR:

1. Please merge the PR only after the tests have passed.
2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

---

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/16664211446 - please use this URL for debugging.}

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/16664736825. Examine the logs at this URL for more detail.}

[mattip]

This will need more work to update ray to use these versions, since it vendors these libraries. The backport of the current patches in ray-project/ray#51673 is still stuck with some failing tests.

[mattip]

Mess. It turns out grpc 1.73 requires bazel rules_java >=8.5.0, which seems to not play well with a WORKSPACE-based bazel workflow. When I update the top-level WORKSPACE with

-- a/WORKSPACE
+++ b/WORKSPACE
@@ -12,20 +12,20 @@ http_archive(
 
 http_archive(
     name = "rules_java",
-    sha256 = "302bcd9592377bf9befc8e41aa97ec02df12813d47af9979e4764f3ffdcc5da8",
+    sha256 = "0868adfca5fc69a60acfbf9615a550319a81bbf779715fb7453c52706994fccf",
+    strip_prefix = "rules_java-8.5.1",
     urls = [
-        "https://github.com/bazelbuild/rules_java/releases/download/7.12.4/rules_java-7.12.4.tar.gz",
+        "https://github.com/bazelbuild/rules_java/archive/refs/tags/8.5.1.tar.gz",
     ],
 )
 
-load("@rules_java//java:repositories.bzl", "rules_java_dependencies", "rules_java_toolchains")
-
+load("@rules_java//java:repositories.bzl", "rules_java_dependencies")
 rules_java_dependencies()
 
-rules_java_toolchains()
+#load("@rules_java//java:repositories.bzl", "rules_java_toolchains")
+#rules_java_toolchains()

I get an error

ERROR: Failed to load Starlark extension '@compatibility_proxy//:proxy.bzl'.
Cycle in the workspace file detected. This indicates that a repository is used prior to being defined.
The following chain of repository dependencies lead to the missing definition.
 - @compatibility_proxy
This could either mean you have to add the '@compatibility_proxy' repository with a
statement like `http_archive` in your WORKSPACE file (note that transitive dependencies
are not added automatically), or move an existing definition earlier in your WORKSPACE file.