This PR allows users to set the custom monitoring host for built in metrics.

This PR introduces `java.time` alternatives to existing `org.threeten.bp.*` methods, as well as switching internal variables (if any) to `java.time`

The main constraint is to keep the changes backwards compatible, so for each existing threeten method "`method1(org.threeten.bp.Duration)`" we will add an alternative with a _Duration_ (or _Timestamp_ when applicable) suffix: "`method1Duration(java.time.Duration)`".

For most cases, the implementation will be held in the `java.time` method and the old threeten method will just delegate the call to it. However, for the case of abstract classes, the implementation will be kept in the threeten method to avoid breaking changes (i.e. users that already overloaded the method in their user code).

#3471)

* chore(spanner): support multiplexed session for rw transactions in executor

* chore(spanner): lint fix

…#3231)

* feat(spanner): support multiplexed session for Partitioned read or query.

* chore(spanner): lint fixes

* feat(spanner): support multiplexed session for Partitioned DML operations.

* lint(spanner): javadoc fixes.

* feat(spanner): Updated unit tests of Partitioned operations for Multiplexed Session.

* feat(spanner): Updated unit tests of Partitioned operations for Multiplexed Session.

* lint(spanner): Apply suggestions from code review

Co-authored-by: Knut Olav Løite <[email protected]>

* lint(spanner): Apply suggestions from code review

Co-authored-by: Knut Olav Løite <[email protected]>

* feat(spanner): Modified BatchClientImpl to store multiplexed session and create fresh session after expiration date.

* feat(spanner): Removed env variable for Partitioned Ops ensuring that Multiplexed Session for Partitioned Ops is not available to customers.

* lint(spanner): Removed unused variables.

---------

Co-authored-by: Knut Olav Løite <[email protected]>

Multiple tests were skipped on the Emulator, because the features that
are covered by these tests were originally not supported on the
Emulator. These features are now available on the Emulator, and the
tests can be enabled.

* ci(spanner): Fix nightly job permission issue

* update scope for surefire-junit4

The Connection API by default uses either a platform thread or a virtual thread
for each connection to execute and control the statements of that connection. This
is used to enable asynchronous execution of statements and allows a statement to
be cancelled by just interrupting this thread. Both these use cases are however
not (or only very rarely) used by the most common users of the Connection API;
the JDBC driver and PGAdapter. PGAdapter uses the PostgreSQL wire-protocol, which
by design is synchronous, and JDBC is also a synchronous API. The latter has a
cancel() method that currently requires this threading model, but this can be
modified in the JDBC driver.

Using a direct executor instead of a single-threaded executor per connection can
save one thread per connection.

The option is intentionally made package-private, so the above-mentioned
frameworks can set it by default without it becoming part of the public API.

Adds support for `set local retry_aborts_internally=true|false` in the
Connection API. This change also adds the parsing infrastructure that is
needed to support `set local` for all connection variables. Support for
this will be added to other connection variables in follow-up pull requests.

* feat(spanner): Releasing Multiplexed session for blind write.

* fix(spanner): Added exception for `setUseMultiplexedSessionBlindWrite` in Clirr check. Removing this is safe as it's not used by customers.

* fix(spanner): Fixed unit test for multiplexed session.

* ci(spanner): clean up unused kokoro configurations

* chore: generate libraries at Tue Dec 10 09:54:10 UTC 2024

---------

Co-authored-by: cloud-java-bot <[email protected]>

… in systest. (#3545)

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

Reset the default to using a platform thread for connections. This was the
default before adding an option for setting the executor type, and the new
default is causing problems with the async Connection API.

Fixes #3541

#3523)

* chore: Update generation configuration at Wed Dec  4 02:29:01 UTC 2024

* chore: Update generation configuration at Thu Dec  5 02:29:11 UTC 2024

* chore: Update generation configuration at Fri Dec  6 02:28:46 UTC 2024

* chore: generate libraries at Fri Dec  6 02:29:25 UTC 2024

* chore: Update generation configuration at Sat Dec  7 02:28:09 UTC 2024

* chore: Update generation configuration at Tue Dec 10 02:29:37 UTC 2024

* chore: Update generation configuration at Wed Dec 11 02:28:47 UTC 2024

* chore: Update generation configuration at Thu Dec 12 02:29:08 UTC 2024

* chore: generate libraries at Thu Dec 12 02:29:50 UTC 2024

* chore: Update generation configuration at Fri Dec 13 02:29:25 UTC 2024

* chore: Update generation configuration at Fri Dec 13 16:21:35 UTC 2024

* chore: generate libraries at Fri Dec 13 16:22:12 UTC 2024

* update workflow script

---------

Co-authored-by: rahul2393 <[email protected]>
Co-authored-by: Joe Wang <[email protected]>

* chore(main): release 6.83.0

* chore: generate libraries at Fri Dec 13 17:19:20 UTC 2024

---------

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