Fix CVEs in google-cloud via dependency updates and tree tracing

[sidhdirenge]

Traced dependency tree and updated snappy-java (1.1.10.5), avro (1.11.4), jackson-databind (2.14.0), protobuf-java (3.25.5), and guava (31.1-jre).

[gemini-code-assist]

Code Review

This pull request updates several dependency versions in the pom.xml file, including Apache Avro, Guava, Protocol Buffers, Jackson Databind, and Snappy Java. The reviewer recommends avoiding hardcoded version numbers within the dependency declarations. Instead, the project should continue using Maven properties (such as ${avro.version}, ${guava.version}, ${google.protobuf.java.version}, and ${jackson.core.version}) and update their definitions in the <properties> section to ensure POM consistency and maintainability.

[gemini-code-assist]

Instead of hardcoding the version 1.11.4 directly in the dependency, you should continue using the property ${avro.version}. The property avro.version is already defined as 1.11.4 in the <properties> section of this POM. Hardcoding it here bypasses the property and reduces maintainability.

Suggested change

	<version>1.11.4</version>
	<version>${avro.version}</version>

[gemini-code-assist]

Instead of hardcoding the version 31.1-jre directly in the dependency, you should continue using the property ${guava.version} and update the <guava.version> property in the <properties> section (line 79) to 31.1-jre. This keeps the POM consistent and avoids leaving unused or outdated properties.

Suggested change

	<version>31.1-jre</version>
	<version>${guava.version}</version>

[gemini-code-assist]

Instead of hardcoding the version 3.25.5 directly in the dependency, you should continue using the property ${google.protobuf.java.version} and update the <google.protobuf.java.version> property in the <properties> section (line 77) to 3.25.5. This keeps the POM consistent and avoids leaving unused or outdated properties.

Suggested change

	<version>3.25.5</version>
	<version>${google.protobuf.java.version}</version>

[gemini-code-assist]

Instead of hardcoding the version 2.14.0 directly in the dependency, you should continue using the property ${jackson.core.version} and update the <jackson.core.version> property in the <properties> section (line 84) to 2.14.0. This keeps the POM consistent and avoids leaving unused or outdated properties.

Suggested change

	<version>2.14.0</version>
	<version>${jackson.core.version}</version>