deps: update all tracing and telemetry dependencies

[olavloite]

Update all tracing and telemetry dependencies in one PR, and create property definitions for versions that should be updated in sync.

[gemini-code-assist]

Summary of Changes

Hello @olavloite, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request systematically updates and centralizes the management of tracing and telemetry-related dependencies across several project modules. The primary goal is to ensure that the project leverages the latest features and fixes from Google Cloud's monitoring and tracing libraries, while also improving the maintainability of dependency versions through the introduction of shared Maven properties. This change enhances the overall stability and future-proofing of the project's observability components.

Highlights

• Centralized Version Management: Introduced new Maven properties (google.cloud.monitoring.version and google.cloud.opentelemetry.version) to manage dependency versions centrally, improving consistency and simplifying future updates across modules.
• Google Cloud Monitoring Update: Updated google-cloud-monitoring, proto-google-cloud-monitoring-v3, and grpc-google-cloud-monitoring-v3 dependencies to version 3.81.0 across benchmarks/pom.xml and google-cloud-spanner/pom.xml.
• OpenTelemetry and Google Cloud Trace Updates: Updated exporter-trace to 0.36.0 and google-cloud-trace to 2.79.0 in both google-cloud-spanner-executor and google-cloud-spanner modules.
• New OpenTelemetry Dependency: Added shared-resourcemapping (version 0.36.0) to google-cloud-spanner-executor/pom.xml to support OpenTelemetry resource mapping, and included it in the maven-dependency-plugin's ignored dependencies.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request effectively updates several tracing and telemetry dependencies and introduces properties to manage their versions, which is a great improvement for maintainability. My review includes a few suggestions to apply this practice more consistently across the POM files by replacing some remaining hardcoded versions with properties. This will further align the changes with the PR's goal.

[gemini-code-assist]

To improve maintainability and consistency with the goal of this PR, consider defining a property for the google.cloud.opentelemetry dependencies as well. The dependencies exporter-trace (line 53) and exporter-metrics (line 58) use a hardcoded version 0.36.0. You can define the property here and then use it for those dependencies.

    <google.cloud.monitoring.version>3.81.0</google.cloud.monitoring.version>
    <google.cloud.opentelemetry.version>0.36.0</google.cloud.opentelemetry.version>

[gemini-code-assist]

This version is hardcoded. The proto-google-cloud-trace-v1 dependency on line 153 also has a hardcoded version 2.79.0. To align with the goal of this PR to use properties for synchronized versions, consider defining a property like <google.cloud.trace.version>2.79.0</google.cloud.trace.version> in the <properties> section and using it here and for the other dependency.

Suggested change

	<version>2.79.0</version>
	<version>${google.cloud.trace.version}</version>

[gemini-code-assist]

The version for exporter-trace is hardcoded. To improve maintainability and align with the PR's goal, please define a property <google.cloud.opentelemetry.version>0.36.0</google.cloud.opentelemetry.version> in the <properties> section of this POM (e.g., on line 19) and use it here.

Suggested change

	<version>0.36.0</version>
	<version>${google.cloud.opentelemetry.version}</version>

[gemini-code-assist]

The version for google-cloud-trace is hardcoded. The proto-google-cloud-trace-v1 dependency on line 515 also has a hardcoded version 2.79.0. To improve maintainability, consider defining a property like <google.cloud.trace.version>2.79.0</google.cloud.trace.version> in the <properties> section (e.g., on line 19) and using it for both dependencies.

Suggested change

	<version>2.79.0</version>
	<version>${google.cloud.trace.version}</version>