deps: update dependency com.google.cloud:google-cloud-spanner-bom to v6.89.0 (#1961)

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

* chore: update test cases and regenerate documentation

The Spanner client now also uses a multiplexed session to determine the database
dialect that is in use. This means that BatchCreateSessions is not being called
at all in many cases.

Also re-generates the connection properties documentation. The typo in the
description of the new connection property must be fixed in the Spanner
client, as the list here is generated based on the source in the client.

* chore: run code formatter

---------

Co-authored-by: Knut Olav Løite <koloite@gmail.com>

Author: renovate-bot

documentation/connection_properties.md

@@ -31,6 +31,7 @@ The 'Context' value indicates whether the property can only be set when a connec
 | enableextendedtracing | Include the SQL string in the OpenTelemetry traces that are generated by this connection. The SQL string is added as the standard OpenTelemetry attribute 'db.statement'. |  | true, false | STARTUP |
 | encodedcredentials | Base64-encoded credentials to use for this connection. If neither this property or a credentials location are set, the connection will use the default Google Cloud credentials for the runtime environment. |  |  | STARTUP |
 | endpoint | The endpoint that the JDBC driver should connect to. The default is the default Spanner production endpoint when autoConfigEmulator=false, and the default Spanner emulator endpoint (localhost:9010) when autoConfigEmulator=true. This property takes precedence over any host name at the start of the connection URL. |  |  | STARTUP |
+| isexperimentalhost | Set this value to true for communication with a Experimental Host. | false | true, false | STARTUP |
 | keeptransactionalive | Enabling this option will trigger the connection to keep read/write transactions alive by executing a SELECT 1 query once every 10 seconds if no other statements are being executed. This option should be used with caution, as it can keep transactions alive and hold on to locks longer than intended. This option should typically be used for CLI-type application that might wait for user input for a longer period of time. | false | true, false | USER |
 | lenient | Silently ignore unknown properties in the connection string/properties (true/false) | false | true, false | STARTUP |
 | maxcommitdelay | The max delay that Spanner may apply to commit requests to improve throughput. |  |  | USER |

pom.xml

@@ -61,7 +61,7 @@
       <dependency>
         <groupId>com.google.cloud</groupId>
         <artifactId>google-cloud-spanner-bom</artifactId>
-        <version>6.88.0</version>
+        <version>6.89.0</version>
         <type>pom</type>
         <scope>import</scope>
       </dependency>

samples/spring-data-jdbc/pom.xml

@@ -30,7 +30,7 @@
       <dependency>
         <groupId>com.google.cloud</groupId>
         <artifactId>google-cloud-spanner-bom</artifactId>
-        <version>6.88.0</version>
+        <version>6.89.0</version>
         <scope>import</scope>
         <type>pom</type>
       </dependency>

src/test/java/com/google/cloud/spanner/jdbc/JdbcGrpcErrorTest.java

@@ -430,8 +430,7 @@ public void transactionalCreateSession() throws SQLException {
 
   @Test
   public void readOnlyCreateSession() throws SQLException {
-    mockSpanner.setBatchCreateSessionsExecutionTime(
-        SimulatedExecutionTime.ofException(serverException));
+    mockSpanner.setCreateSessionExecutionTime(SimulatedExecutionTime.ofException(serverException));
     try (java.sql.Connection connection = createConnection()) {
       connection.setAutoCommit(false);
       connection.setReadOnly(true);

src/test/java/com/google/cloud/spanner/jdbc/MultiplexedSessionsMockServerTest.java

@@ -205,8 +205,6 @@ public void testUsesMultiplexedSessionInCombinationWithSessionPoolOptions() thro
     CreateSessionRequest request = mockSpanner.getRequestsOfType(CreateSessionRequest.class).get(0);
     assertTrue(request.getSession().getMultiplexed());
     // There should be no regular sessions in use.
-    // However, the query that detects the dialect that is used, uses a regular session.
-    // This should be fixed in the Java client.
-    assertEquals(1, mockSpanner.countRequestsOfType(BatchCreateSessionsRequest.class));
+    assertEquals(0, mockSpanner.countRequestsOfType(BatchCreateSessionsRequest.class));
   }
 }