Upgrade everything!

[Wyverald]

What started out as an attempt to upgrade gRPC has snowballed into this monster...

• Upgrades gRPC to the latest version, including the Java bindings from grpc-java
  • grpc-java actually specifies Maven overrides, causing rules_jvm_external's references to io.grpc.* and com.google.protobuf.* to alias to actual Bazel build targets in @grpc-java and @protobuf. So this effectively means we're no longer using the gRPC jars from Maven
  • To support these overrides, our custom patch for rules_jvm_external had to be updated to include the alias targets in the BUILD.vendor file.
• The upgrade to gRPC means we now use the latest googleapis from BCR
  • This means we can remove the vendored copy of those protos. Updated all references to googleapis protos across the codebase.
• The upgrade to gRPC means we now use the latest version of protobuf
  • This ran into some trouble with the concurrent work to move Bazel's proto rules into protobuf, which means that we currently have to use the protobuf version from HEAD.
  • We also have to patch out protobuf's dependency on rules_rust, as it introduces a lot of dependency bloat and makes it impossible to build a bootstrap distribution archive
  • The dependency on upb is completely removed.

Fixes #22719

[Wyverald]

Currently stuck on making HEAD Bazel build itself.

At the source checkout state of this PR, I can run USE_BAZEL_VERSION=7.3.1 bazelisk build src:bazel and that's all fine. But if I then use the just-built bazel (cp bazel-bin/src/bazel ~/elsewhere/bazel; ~/elsewhere/bazel build src:bazel), then I get errors like this:

ERROR: /Users/wyv/github/bazel2/src/main/java/com/google/devtools/build/lib/buildeventstream/proto/BUILD:23:14: in deps attribute of proto_library rule //src/main/java/com/google/devtools/build/lib/buildeventstream/proto:build_event_stream_proto: '@@protobuf+//src/google/protobuf:timestamp_proto' does not have mandatory providers: 'ProtoInfo'. Since this rule was created by the macro 'proto_library', the error might have been caused by the macro implementation

Using Bazel 7.3.1 and the just-built Bazel to cquery the provider list, the difference is evident:

$ USE_BAZEL_VERSION=7.3.1 bazelisk cquery "'@@protobuf+//src/google/protobuf:duration_proto'" --output=starlark --starlark:expr="providers(target)"
INFO: Analyzed target @@protobuf+//src/google/protobuf:duration_proto (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
{"LicenseInfo": <instance of provider LicenseInfo>, "@@_builtins//:common/proto/proto_info.bzl%ProtoInfo": struct( [...]
$ ~/elsewhere/bazel cquery "'@@protobuf+//src/google/protobuf:duration_proto'" --output=starlark --starlark:expr="providers(target)"
INFO: Analyzed target @@protobuf+//src/google/protobuf:duration_proto (128 packages loaded, 2060 targets configured).
INFO: Found 1 target...
{"LicenseInfo": <instance of provider LicenseInfo>, "@@protobuf+//bazel/private:proto_info.bzl%ProtoInfo": struct( [...]

it looks like on HEAD Bazel, the proto_library targets export the ProtoInfo from protobuf, but the rule itself for some reason expects deps to have the ProtoInfo from builtins.

[Wyverald]

The issue above has been addressed by 3cb5bea. This is now ready for review.

[meteorcloudy]

Nice work!!

[meteorcloudy]

@Wyverald Can you merge this one since there are many BUILD file changes. We'll also need a separate PR to delete googleapis from third_party.