SOLR-18206 Use google-cloud-bom instead of individual lib pinning

[janhoy]

https://issues.apache.org/jira/browse/SOLR-18206

This PR supersedes #4098 (originally opened by Renovate/SolrBot) and expands its scope significantly.

Instead of just bumping individual Google Cloud library versions, this PR switches the GCS repository module to resolve all Google Cloud dependencies via the google-cloud-bom Bill of Materials, then bumps the BOM to the latest version (0.261.0). This simplifies future upgrades — only the BOM version needs updating, and all transitive Google Cloud
libraries are automatically aligned.

Changes

• google-cloud-bom bumped from 0.224.0 → 0.261.0
• grpc-bom bumped from 1.65.1 → 1.80.0
• Removed explicit version pins for Google Cloud libraries now managed by the BOM (google-cloud-storage, google-cloud-nio, google-cloud-core, google-cloud-core-http, google-auth, google-api-gax)
• Excluded unnecessary Google OTel transitive dependencies pulled in by the GCS module
• Added consistentResolution.useCompileClasspathVersions() to the GCS module to align dependency resolution across configurations
• Updated all lockfiles and license SHA1 files accordingly

Key transitive version changes (via BOM 0.261.0)

Library	Before	After
google-cloud-storage	2.27.0	2.67.0
google-cloud-nio	0.127.3	0.131.0
google-cloud-core	2.60.1	2.69.0
google-auth	1.19.0	1.46.0
gax	2.70.x	2.79.0
grpc-*	1.65.1	1.80.0

Closes #3117

[janhoy]

Suggested change

	title: Move Google cloud dependencies to resolving google-cloud-bom. Bump to 0.261.0 and grpc-bom to 1.80.0
	title: Resolve Google cloud dependencies using google-cloud-bom. Bump it to 0.261.0 and grpc-bom to 1.80.0

[janhoy]

We should probably try the same trick (removing version.ref) for the grpc-* family as well, although they use a common version.

[janhoy]

Crave tests failed with

Selecting project Solr (id:39)
Picking up local changes (if any)...
Waiting for build id:269589 to start...
Setting up workspace (this could take some time)...
CreateImageFromSnapshotFailed Exception({'errors': [{'code': 'QUOTA_EXCEEDED', 'message': "Quota 'SSD_TOTAL_GB' exceeded.  Limit: 20480.0 in region us-central1.", 'errorDetails': [{'quotaInfo': {'metricName': 'compute.googleapis.com/ssd_total_storage', 'limitName': 'SSD-TOTAL-GB-per-project-region', 'dimensions': {'region': 'us-central1'}, 'limit': 20480}}]}]}) 

Have anyone seen it before? Could it be the build cancellations in #4318 that is not working as it should and leaves behind old workspaces? Who has the foo to clean up?