🤖 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).

* Add sample and test.

* format

* format

* 🦉 Updates from OwlBot post-processor

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

* Update samples/snippets/src/main/java/com/example/spanner/SetMaxCommitDelaySample.java

* chore: removed unused import

---------

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
Co-authored-by: Arpan Mishra <[email protected]>
Co-authored-by: Knut Olav Løite <[email protected]>

…to v6.65.0 (#3053)

* chore(deps): update dependency com.google.cloud:google-cloud-spanner to v6.65.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>

* chore(spanner): add multiplexed session flag for executor code

* chore(spanner): clirr fix

* chore(spanner): refactor doublt to boolean flag

* chore(spanner): clirr fix

* 🦉 Updates from OwlBot post-processor

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

* chore(spanner): code refactoring

* chore(spanner): add validation for ratio flag

* chore(spanner): add logs

---------

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

#3060)

We are not updating the value of multiplexed session within the background thread. So there is no need to hold a lock. Removing this lock can potentially improve performance.

#3058)

* chore: mark multiplexed session unit test as required

* mark java8 as required

…me (#3062)

* The existing setup using JMH produces flaky results at time due to thread safe scope variables and also it lacks the ability to pass different parameters from command-line.
* This is a more light-weight setup which allows to pass params from command-line and keeps the setup much simpler.
* This util also allows us to export metrics/traces directly to cloud monitoring so that its easy to visualize and compare stats.

1. Add support for FLOAT32 in cloud client executor
2. Also allow integration tests to run FLOAT32 type against prod

#3065)

Without the hint, GAX would do a round-robin on channels. In theory, a random hint would give a better performance than round robin at a high QPS workload. Also YCSB benchmarks suggest having the hint is better for higher QPS.

…3.43.0 (#3066)

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