feat(bigtableadmin): update the api

#### bigtableadmin:v2

The following keys were added:
- schemas.AutoscalingTargets.properties.storageUtilizationGibPerNode (Total Keys: 2)

Author: yoshi-automation

docs/dyn/bigtableadmin_v2.projects.instances.clusters.html

@@ -132,6 +132,7 @@ <h3>Method Details</h3>
       },
       &quot;autoscalingTargets&quot;: { # The Autoscaling targets for a Cluster. These determine the recommended nodes. # Required. Autoscaling targets for this cluster.
         &quot;cpuUtilizationPercent&quot;: 42, # The cpu utilization that the Autoscaler should be trying to achieve. This number is on a scale from 0 (no utilization) to 100 (total utilization), and is limited between 10 and 80, otherwise it will return INVALID_ARGUMENT error.
+        &quot;storageUtilizationGibPerNode&quot;: 42, # The storage utilization that the Autoscaler should be trying to achieve. This number is limited between 2560 (2.5TiB) and 5120 (5TiB) for a SSD cluster and between 8192 (8TiB) and 16384 (16TiB) for an HDD cluster, otherwise it will return INVALID_ARGUMENT error. If this value is set to 0, it will be treated as if it were set to the default value: 2560 for SSD, 8192 for HDD.
       },
     },
   },
@@ -216,6 +217,7 @@ <h3>Method Details</h3>
       },
       &quot;autoscalingTargets&quot;: { # The Autoscaling targets for a Cluster. These determine the recommended nodes. # Required. Autoscaling targets for this cluster.
         &quot;cpuUtilizationPercent&quot;: 42, # The cpu utilization that the Autoscaler should be trying to achieve. This number is on a scale from 0 (no utilization) to 100 (total utilization), and is limited between 10 and 80, otherwise it will return INVALID_ARGUMENT error.
+        &quot;storageUtilizationGibPerNode&quot;: 42, # The storage utilization that the Autoscaler should be trying to achieve. This number is limited between 2560 (2.5TiB) and 5120 (5TiB) for a SSD cluster and between 8192 (8TiB) and 16384 (16TiB) for an HDD cluster, otherwise it will return INVALID_ARGUMENT error. If this value is set to 0, it will be treated as if it were set to the default value: 2560 for SSD, 8192 for HDD.
       },
     },
   },
@@ -256,6 +258,7 @@ <h3>Method Details</h3>
           },
           &quot;autoscalingTargets&quot;: { # The Autoscaling targets for a Cluster. These determine the recommended nodes. # Required. Autoscaling targets for this cluster.
             &quot;cpuUtilizationPercent&quot;: 42, # The cpu utilization that the Autoscaler should be trying to achieve. This number is on a scale from 0 (no utilization) to 100 (total utilization), and is limited between 10 and 80, otherwise it will return INVALID_ARGUMENT error.
+            &quot;storageUtilizationGibPerNode&quot;: 42, # The storage utilization that the Autoscaler should be trying to achieve. This number is limited between 2560 (2.5TiB) and 5120 (5TiB) for a SSD cluster and between 8192 (8TiB) and 16384 (16TiB) for an HDD cluster, otherwise it will return INVALID_ARGUMENT error. If this value is set to 0, it will be treated as if it were set to the default value: 2560 for SSD, 8192 for HDD.
           },
         },
       },
@@ -308,6 +311,7 @@ <h3>Method Details</h3>
       },
       &quot;autoscalingTargets&quot;: { # The Autoscaling targets for a Cluster. These determine the recommended nodes. # Required. Autoscaling targets for this cluster.
         &quot;cpuUtilizationPercent&quot;: 42, # The cpu utilization that the Autoscaler should be trying to achieve. This number is on a scale from 0 (no utilization) to 100 (total utilization), and is limited between 10 and 80, otherwise it will return INVALID_ARGUMENT error.
+        &quot;storageUtilizationGibPerNode&quot;: 42, # The storage utilization that the Autoscaler should be trying to achieve. This number is limited between 2560 (2.5TiB) and 5120 (5TiB) for a SSD cluster and between 8192 (8TiB) and 16384 (16TiB) for an HDD cluster, otherwise it will return INVALID_ARGUMENT error. If this value is set to 0, it will be treated as if it were set to the default value: 2560 for SSD, 8192 for HDD.
       },
     },
   },
@@ -369,6 +373,7 @@ <h3>Method Details</h3>
       },
       &quot;autoscalingTargets&quot;: { # The Autoscaling targets for a Cluster. These determine the recommended nodes. # Required. Autoscaling targets for this cluster.
         &quot;cpuUtilizationPercent&quot;: 42, # The cpu utilization that the Autoscaler should be trying to achieve. This number is on a scale from 0 (no utilization) to 100 (total utilization), and is limited between 10 and 80, otherwise it will return INVALID_ARGUMENT error.
+        &quot;storageUtilizationGibPerNode&quot;: 42, # The storage utilization that the Autoscaler should be trying to achieve. This number is limited between 2560 (2.5TiB) and 5120 (5TiB) for a SSD cluster and between 8192 (8TiB) and 16384 (16TiB) for an HDD cluster, otherwise it will return INVALID_ARGUMENT error. If this value is set to 0, it will be treated as if it were set to the default value: 2560 for SSD, 8192 for HDD.
       },
     },
   },

docs/dyn/bigtableadmin_v2.projects.instances.html

@@ -148,6 +148,7 @@ <h3>Method Details</h3>
           },
           &quot;autoscalingTargets&quot;: { # The Autoscaling targets for a Cluster. These determine the recommended nodes. # Required. Autoscaling targets for this cluster.
             &quot;cpuUtilizationPercent&quot;: 42, # The cpu utilization that the Autoscaler should be trying to achieve. This number is on a scale from 0 (no utilization) to 100 (total utilization), and is limited between 10 and 80, otherwise it will return INVALID_ARGUMENT error.
+            &quot;storageUtilizationGibPerNode&quot;: 42, # The storage utilization that the Autoscaler should be trying to achieve. This number is limited between 2560 (2.5TiB) and 5120 (5TiB) for a SSD cluster and between 8192 (8TiB) and 16384 (16TiB) for an HDD cluster, otherwise it will return INVALID_ARGUMENT error. If this value is set to 0, it will be treated as if it were set to the default value: 2560 for SSD, 8192 for HDD.
           },
         },
       },

googleapiclient/discovery_cache/documents/bigtableadmin.v2.json

@@ -1860,7 +1860,7 @@
       }
     }
   },
-  "revision": "20220430",
+  "revision": "20220506",
   "rootUrl": "https://bigtableadmin.googleapis.com/",
   "schemas": {
     "AppProfile": {
@@ -1963,6 +1963,11 @@
           "description": "The cpu utilization that the Autoscaler should be trying to achieve. This number is on a scale from 0 (no utilization) to 100 (total utilization), and is limited between 10 and 80, otherwise it will return INVALID_ARGUMENT error.",
           "format": "int32",
           "type": "integer"
+        },
+        "storageUtilizationGibPerNode": {
+          "description": "The storage utilization that the Autoscaler should be trying to achieve. This number is limited between 2560 (2.5TiB) and 5120 (5TiB) for a SSD cluster and between 8192 (8TiB) and 16384 (16TiB) for an HDD cluster, otherwise it will return INVALID_ARGUMENT error. If this value is set to 0, it will be treated as if it were set to the default value: 2560 for SSD, 8192 for HDD.",
+          "format": "int32",
+          "type": "integer"
         }
       },
       "type": "object"