chore: bump cloud.google.com/go/compute/metadata from 0.2.3 to 0.7.0

[dependabot]

Bumps cloud.google.com/go/compute/metadata from 0.2.3 to 0.7.0.

Release notes

Sourced from cloud.google.com/go/compute/metadata's releases.

compute/metadata: v0.7.0

0.7.0 (2025-05-13)

Features

• compute/metadata: Allow canceling GCE detection (#11786) (78100fe)

managedkafka: v0.5.2

0.5.2 (2025-04-30)

Documentation

• managedkafka: A comment for message TaskRetryPolicy is changed (#12082) (4c53c42)

oracledatabase: v0.5.0

0.5.0 (2025-04-30)

Features

• oracledatabase: Re-enable gRPC support (#12075) (19c60f9)

visionai: v0.4.5

0.4.5 (2025-04-15)

Bug Fixes

• visionai: Update google.golang.org/api to 0.229.0 (3319672)

memorystore: v0.3.0

0.3.0 (2025-05-06)

Features

• memorystore: A new field async_instance_endpoints_deletion_enabled is added to message .google.cloud.memorystore.v1.Instance (2f22244)
• memorystore: A new field automated_backup_config is added to message .google.cloud.memorystore.v1.Instance (2f22244)
• memorystore: A new field backup_collection is added to message .google.cloud.memorystore.v1.Instance (2f22244)
• memorystore: A new field cross_instance_replication_config is added to message .google.cloud.memorystore.v1.Instance (2f22244)
• memorystore: A new field gcs_source is added to message .google.cloud.memorystore.v1.Instance (2f22244)
• memorystore: A new field maintenance_policy is added to message .google.cloud.memorystore.v1.Instance (2f22244)
• memorystore: A new field maintenance_schedule is added to message .google.cloud.memorystore.v1.Instance (2f22244)
• memorystore: A new field managed_backup_source is added to message .google.cloud.memorystore.v1.Instance (2f22244)
• memorystore: A new field ondemand_maintenance is added to message .google.cloud.memorystore.v1.Instance (2f22244)
• memorystore: A new field port is added to message .google.cloud.memorystore.v1.PscConnection (2f22244)
• memorystore: A new field psc_attachment_details is added to message .google.cloud.memorystore.v1.Instance (2f22244)
• memorystore: A new field target_engine_version is added to message .google.cloud.memorystore.v1.Instance (2f22244)

... (truncated)

Changelog

Sourced from cloud.google.com/go/compute/metadata's changelog.

v0.7.0

• Release of a client library for Spanner. See the blog post. Note that although the Spanner service is beta, the Go client library is alpha.

v0.6.0

• Beta release of BigQuery, DataStore, Logging and Storage. See the blog post.

• bigquery:

  • struct support. Read a row directly into a struct with RowIterator.Next, and upload a row directly from a struct with Uploader.Put. You can also use field tags. See the [package documentation][cloud-bigquery-ref] for details.

  • The ValueList type was removed. It is no longer necessary. Instead of

  var v ValueList
  ... it.Next(&v) ..

  use

  var v []Value
  ... it.Next(&v) ...

  • Previously, repeatedly calling RowIterator.Next on the same []Value or ValueList would append to the slice. Now each call resets the size to zero first.

  • Schema inference will infer the SQL type BYTES for a struct field of type []byte. Previously it inferred STRING.

  • The types uint, uint64 and uintptr are no longer supported in schema inference. BigQuery's integer type is INT64, and those types may hold values that are not correctly represented in a 64-bit signed integer.

v0.5.0

• bigquery:
  • The SQL types DATE, TIME and DATETIME are now supported. They correspond to the Date, Time and DateTime types in the new cloud.google.com/go/civil package.
  • Support for query parameters.
  • Support deleting a dataset.
  • Values from INTEGER columns will now be returned as int64, not int. This

... (truncated)

Commits

• 2e6a95e pubsub: fix flaky streaming retry test
• 581b839 pubsub: check early if streaming iterator is already drained
• cc13a9b spanner: fix time.Time comparisons for upcoming Go1.9 monotonic times
• 1ba9ec4 spanner: remove most logging from tests
• 11737a0 spanner: skip some tests in short mode
• 7bcba8a datastore: DRY up loading entity code
• df9740f regenerate toolkit client
• 960c768 trace: export tracing scopes
• 8b0ab47 logadmin: retry on CreateMetric and UpdateMetric
• 2066696 trace: clarify how gRPC options work
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.