🤖 I have created a release *beep* *boop*
---


### Updating meta-information for bleeding-edge SNAPSHOT release.

---
This PR was generated with [Release Please](https://togithub.com/googleapis/release-please). See [documentation](https://togithub.com/googleapis/release-please#release-please).

* chore: remove obsolete release job configs

* remove extra comma

* test: disable proto column tests

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

---------

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

* feat: support Directed Read in Connection API

Adds support for setting Directed Read options in the Connection API.
The value must be a valid JSON representation of a DirectedReadOptions
protobuf instance.

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

* chore: address review comments

* fix: verify that DirectedRead is not used for DML

---------

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

…cies to v3.24.0 (#2856)

* deps: update dependency com.google.cloud:google-cloud-shared-dependencies to v3.24.0

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

---------

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

The cleanup function used to remove old test databases did not remove the drop protection flag before trying to drop a database.

* chore: fix session acquire timeout test

The test for session acquire timeout did not actually do what it
was supposed to do, as it did not check that a timeout was actually
registered. This again also caused it to busy-wait for 5 seconds
to times (MinSessions=0 and MinSessions=1). This fixes both the
actual test, and reduces the overall test time by about 10 seconds.

* chore: address review comments

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

---------

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

The virtual threads util that tries to create a virtual thread factory on JVMs that support this would fail on Java 20, because:
1. Java 20 supports virtual threads as an experimental feature. This means that the code is present.
2. The feature is by default disabled, and throws an UnsupportedOperationException.

This fix takes the above into account and returns null if a user tries to create a virtual threads factory on Java 20 with experimental features disabled.

Statements that were executed using the Connection API and that were not
found in the statement cache (that is; it was the first time it was
executed), would not use the default query options that had been set for
the connection. This would mean that for example an optimizer version
that had been set for the connection would not be used the first time a
given query string would be executed using a connection. All subsequent
executions of the statement would use specified optimizer version.

This change ensures that both the first and all following executions of
the statement use the default query options that have been set.

* add commit delay options

* feat: add max_commit_delay options for commit requests

* Point stuff to devel

* Make samples work with devel. Add a typo.

* Cleanup stuff

* Remove duplicate definitions.

* Fix merge conflict.

* Remove SpannerSample pointing to devel.

* Add some parans

* Add a unit test to ensure unset commit delay is properly propagated

* Add an integration test.

* change maxCommitDelayInMillis of type Int to maxCommitDelay of type Duration.

* Format

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

---------

Co-authored-by: rahul yadav <[email protected]>
Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

This PR adds support for [OpenTelemetry](https://opentelemetry.io/) Instrumentation for Traces and Metrics. 

Add dependency for [OpenTelemetrySDK](https://opentelemetry.io/docs/instrumentation/java/manual/#initialize-the-sdk) and required [exporters](https://opentelemetry.io/docs/instrumentation/java/exporters/).

Create OpenTelemetry object with required MeterProvider and TracerProvider exporter . Inject OpenTelemetry object via SpannerOptions or register as Global

`
OpenTelemetry openTelemetry = OpenTelemetrySdk.builder()
              .setPropagators(ContextPropagators.create(W3CTraceContextPropagator.getInstance()))
              .setTracerProvider(tracerProvider)
              .setMeterProvider(sdkMeterProvider)
              .build;

SpannerOptions options = SpannerOptions.newBuilder().setOpenTelemetry(openTelemetry).build();
`

 By default, OpenTelemetry traces are not enabled. To enable OpenTelemetry traces , call `SpannerOptions.enableOpenTelemetryTraces()` in startup of your application. Enabling OpenTelemetry traces will disable OpenCensus traces. Both OpenCensus and OpenTelemetry traces can not be enabled at the same time.

* fix: cast for Proto type

* fix: add null check

* feat(spanner): add ENUM compatibility with getLongArray

* feat: fix argument

* feat: fix bug

* ci: unmanaged dependency check

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

---------

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>