upgrade Bazel protobuf to 33.1

[benjaminp]

Following up on 58ae5f8, change Bazel's view of the protobuf version to 33.1 too.

This is a bit of an adventure in the bzlmod/WORKSPACE compatibility maze. A few rulesets like rules_java must be upgraded too.

C++ compilation must happen until C++17 now due to the new abseil version required.

Dependency on rules_proto is removed because it has become a superfluous wrapper over rules in the upstream protobuf repo.

It looks like Android Interop Testing build needs some work to include Protobuf dependencies.

[kannanjgithub]

The Linux artifacts build is failing at :grpc-android-interop-testing:packageDebug with errors about missing protobuf Java classes.

[benjaminp]

odd, since that job only involves gradle that I see.

In fact, the full protobuf library that has those dependencies has been purposefully exluded for years; see

grpc-java/android-interop-testing/build.gradle

Line 82 in 283f103

exclude group: 'com.google.protobuf'

. So, anyone know how this ever worked?

[kannanjgithub]

I created a scratch PR #12558 to see what happens if we don't exclude com.google.protobuf group as a transitive dependency in android-interop-testing build. It fails with errors

Execution failed for task ':grpc-android-interop-testing:checkDebugDuplicateClasses'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.CheckDuplicatesRunnable
   > Duplicate class com.google.protobuf.AbstractMessageLite found in modules protobuf-java-3.25.8.jar -> protobuf-java-3.25.8 (com.google.protobuf:protobuf-java:3.25.8) and protobuf-javalite-3.25.8.jar -> protobuf-javalite-3.25.8 (com.google.protobuf:protobuf-javalite:3.25.8)

It still doesn't answer from where it was getting the Protobuf deps when com.google.protobuf was excluded.

[benjaminp]

I think the problem is actually:

* What went wrong:
Execution failed for task ':grpc-android-interop-testing:packageDebug'.
> A failure occurred while executing com.android.build.gradle.tasks.PackageAndroidArtifact$IncrementalSplitterRunnable

I added --stacktrace so maybe the actual error can be revealed...