fix: update dependency io.grpc:grpc-bom to v1.81.0

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
io.grpc:grpc-bom	1.80.0 → 1.81.0

---

Release Notes

grpc/grpc-java (io.grpc:grpc-bom)

v1.81.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM (* 0-3 * * *)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[gemini-code-assist]

Code Review

This pull request updates the grpc-bom version to 1.81.0 in the pom.xml. Feedback indicates that maintaining hardcoded versions for Netty and Protobuf alongside this update creates a risk of binary incompatibility. It is recommended to remove these explicit versions to allow the BOMs to manage them and to ensure grpc-bom is declared before other BOMs to prevent version conflicts under Maven's dependency resolution rules.

[gemini-code-assist]

Updating grpc-bom to 1.81.0 while maintaining hardcoded versions for netty-transport-native-epoll (4.2.12.Final) and protobuf-bom (4.34.1) creates a high risk of runtime binary incompatibilities. gRPC 1.x is generally incompatible with Netty 4.2.x and requires specific Protobuf versions. Per repository guidelines, when updating dependencies not managed by a BOM, verify the version's release date and compatibility with other libraries. Furthermore, because grpc-bom is imported after google-cloud-spanner-bom, Maven's 'first-declaration-wins' rule may cause some gRPC artifacts to use older versions. Consider removing explicit versions for Netty and Protobuf to allow the BOMs to manage them, and ensure grpc-bom is declared before other BOMs.

References

1. When updating dependencies, especially those not managed by a BOM, verify the version's release date to ensure it is current and compatible with other libraries.