fix(spanner): update the API

#### spanner:v1

The following keys were changed:
- schemas.BatchWriteRequest.properties.excludeTxnFromChangeStreams.description
- schemas.DatabaseMoveConfig.properties.databaseId.description
- schemas.DatabaseMoveConfig.properties.encryptionConfig.description

Author: yoshi-automation

discovery/spanner-v1.json

@@ -3406,7 +3406,7 @@
       }
     }
   },
-  "revision": "20250625",
+  "revision": "20250708",
   "rootUrl": "https://spanner.googleapis.com/",
   "schemas": {
     "AdaptMessageRequest": {
@@ -3844,7 +3844,7 @@
       "id": "BatchWriteRequest",
       "properties": {
         "excludeTxnFromChangeStreams": {
-          "description": "Optional. When `exclude_txn_from_change_streams` is set to `true`: * Modifications from all transactions in this batch write operation are not be recorded in change streams with DDL option `allow_txn_exclusion=true` that are tracking columns modified by these transactions. * Modifications from all transactions in this batch write operation are recorded in change streams with DDL option `allow_txn_exclusion=false or not set` that are tracking columns modified by these transactions. When `exclude_txn_from_change_streams` is set to `false` or not set, Modifications from all transactions in this batch write operation are recorded in all change streams that are tracking columns modified by these transactions.",
+          "description": "Optional. If you don't set the `exclude_txn_from_change_streams` option or if it's set to `false`, then any change streams monitoring columns modified by transactions will capture the updates made within that transaction.",
           "type": "boolean"
         },
         "mutationGroups": {
@@ -4703,12 +4703,12 @@
       "id": "DatabaseMoveConfig",
       "properties": {
         "databaseId": {
-          "description": "Required. The unique identifier of the database resource in the Instance. For example if the database uri is projects/foo/instances/bar/databases/baz, the id to supply here is baz.",
+          "description": "Required. The unique identifier of the database resource in the Instance. For example, if the database uri is `projects/foo/instances/bar/databases/baz`, then the id to supply here is baz.",
           "type": "string"
         },
         "encryptionConfig": {
           "$ref": "InstanceEncryptionConfig",
-          "description": "Optional. Encryption configuration to be used for the database in target configuration. Should be specified for every database which currently uses CMEK encryption. If a database currently uses GOOGLE_MANAGED encryption and a target encryption config is not specified, it defaults to GOOGLE_MANAGED. If a database currently uses Google-managed encryption and a target encryption config is specified, the request is rejected. If a database currently uses CMEK encryption, a target encryption config must be specified. You cannot move a CMEK database to a Google-managed encryption database by MoveInstance."
+          "description": "Optional. Encryption configuration to be used for the database in the target configuration. The encryption configuration must be specified for every database which currently uses CMEK encryption. If a database currently uses Google-managed encryption and a target encryption configuration is not specified, then the database defaults to Google-managed encryption. If a database currently uses Google-managed encryption and a target CMEK encryption is specified, the request is rejected. If a database currently uses CMEK encryption, then a target encryption configuration must be specified. You can't move a CMEK database to a Google-managed encryption database using the MoveInstance API."
         }
       },
       "type": "object"

src/apis/spanner/v1.ts

@@ -439,7 +439,7 @@ export namespace spanner_v1 {
    */
   export interface Schema$BatchWriteRequest {
     /**
-     * Optional. When `exclude_txn_from_change_streams` is set to `true`: * Modifications from all transactions in this batch write operation are not be recorded in change streams with DDL option `allow_txn_exclusion=true` that are tracking columns modified by these transactions. * Modifications from all transactions in this batch write operation are recorded in change streams with DDL option `allow_txn_exclusion=false or not set` that are tracking columns modified by these transactions. When `exclude_txn_from_change_streams` is set to `false` or not set, Modifications from all transactions in this batch write operation are recorded in all change streams that are tracking columns modified by these transactions.
+     * Optional. If you don't set the `exclude_txn_from_change_streams` option or if it's set to `false`, then any change streams monitoring columns modified by transactions will capture the updates made within that transaction.
      */
     excludeTxnFromChangeStreams?: boolean | null;
     /**
@@ -1004,11 +1004,11 @@ export namespace spanner_v1 {
    */
   export interface Schema$DatabaseMoveConfig {
     /**
-     * Required. The unique identifier of the database resource in the Instance. For example if the database uri is projects/foo/instances/bar/databases/baz, the id to supply here is baz.
+     * Required. The unique identifier of the database resource in the Instance. For example, if the database uri is `projects/foo/instances/bar/databases/baz`, then the id to supply here is baz.
      */
     databaseId?: string | null;
     /**
-     * Optional. Encryption configuration to be used for the database in target configuration. Should be specified for every database which currently uses CMEK encryption. If a database currently uses GOOGLE_MANAGED encryption and a target encryption config is not specified, it defaults to GOOGLE_MANAGED. If a database currently uses Google-managed encryption and a target encryption config is specified, the request is rejected. If a database currently uses CMEK encryption, a target encryption config must be specified. You cannot move a CMEK database to a Google-managed encryption database by MoveInstance.
+     * Optional. Encryption configuration to be used for the database in the target configuration. The encryption configuration must be specified for every database which currently uses CMEK encryption. If a database currently uses Google-managed encryption and a target encryption configuration is not specified, then the database defaults to Google-managed encryption. If a database currently uses Google-managed encryption and a target CMEK encryption is specified, the request is rejected. If a database currently uses CMEK encryption, then a target encryption configuration must be specified. You can't move a CMEK database to a Google-managed encryption database using the MoveInstance API.
      */
     encryptionConfig?: Schema$InstanceEncryptionConfig;
   }