Update C++ dependencies, roughly matching ones used in python.

[jcferretti]

The goal is actually to build python dependencies with debug info; this is a step.

The change to base-images happened first here: deephaven/deephaven-base-images#116

[devinrsmith]

Execution failed for task ':cpp-client:compareProtobuf'.
Sources do not match expected, re-run :cpp-client:updateProtobuf

[devinrsmith]

I think the version of protobuf will need to be updated in concert with the version grpc supports ie #5299

[Task :proto:proto-backplane-grpc:compileJava FAILED] cannot access GeneratedMessageV3
                Status.newBuilder().setCode(statusCode.getNumber()).setMessage(details).build());
                      ^
  class file for com.google.protobuf.GeneratedMessageV3 not found

./gradlew -q proto:proto-backplane-grpc:dependencyInsight --configuration compileClasspath --dependency proto-google-common-protos 
com.google.api.grpc:proto-google-common-protos:2.22.0
  Variant compile:
    | Attribute Name                 | Provided | Requested    |
    |--------------------------------|----------|--------------|
    | org.gradle.status              | release  |              |
    | org.gradle.category            | library  | library      |
    | org.gradle.libraryelements     | jar      | classes      |
    | org.gradle.usage               | java-api | java-api     |
    | org.gradle.dependency.bundling |          | external     |
    | org.gradle.jvm.environment     |          | standard-jvm |
    | org.gradle.jvm.version         |          | 8            |

com.google.api.grpc:proto-google-common-protos:2.22.0
\--- io.grpc:grpc-protobuf:1.58.0
     +--- compileClasspath (requested io.grpc:grpc-protobuf)
     +--- org.apache.arrow:flight-core:13.0.0 (requested io.grpc:grpc-protobuf:1.56.0)
     |    \--- compileClasspath
     \--- io.grpc:grpc-bom:1.58.0
          \--- compileClasspath

[devinrsmith]

grpc/grpc-java#11015

[devinrsmith]

Looks like grpc-java is sticking with 3.x at this time due to known issues. The advice right now is

For those watching at home and want to be prepared, use protobuf-java 3.25 and protoc 25.

protocolbuffers/protobuf#16452 (comment)

[chipkent]

Do we need to specify the patch version, or are we ok with that changing?

[jcferretti]

That's a specific version, is just the name they gave, in git terms is just some arbitrary string. Mean as far as I understand how the universe works, that won't change when they create a new version.

[chipkent]

1. Were we ultra out of date?
2. Did they change their versioning convention?
3. Do we need to specify the patch version?

[jcferretti]

1. No, they changed in weird ways they numbering, and managed to confuse a lot of people in the process. They also introduced some backwards incompatibilities which is why we can't go directly to 26
2. Yes, see above.
3. No, like the previous answer, that tag should not change.

[alexpeters1208]

R stuff looks good