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

…jdbc to v2.31.3 (#2155)

…v1 to v2.70.0 (#2157)

…v6.98.0 (#2161)

* deps: update dependency com.google.cloud:google-cloud-spanner-bom to v6.98.0

* test: update test cases as mux sessions are default

---------

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

#2158)

The JDBC driver now uses a single multiplexed session for all operations. This applies to all operations in auto-commit mode, in read-only transactions, and in read/write transactions.

One multiplexed session can execute an unlimited number of operations concurrently.

Configuring minSessions and maxSessions in the connection URL is therefore no longer needed for workloads that execute a large number of concurrent transactions.

…8.0 (#2160)

Add an option to use simple PreparedStatement ParameterMetadata that only uses client-side information. This prevents round-trips to Spanner when calling the method PreparedStatement#getParameterMetaData(), for example when these are triggered by frameworks like Spring Data.

This option is experimental and could be removed in future releases.

The option can be enabled by setting the system property `spanner.jdbc.use_simple_parameter_metadata=true`

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