feat(serviceusage): update the api

#### serviceusage:v1beta1

The following keys were added:
- schemas.ConsumerQuotaLimit.properties.supportedLocations (Total Keys: 2)

Author: yoshi-automation

docs/dyn/serviceusage_v1beta1.services.consumerQuotaMetrics.html

@@ -168,6 +168,9 @@ <h3>Method Details</h3>
           },
         },
       ],
+      &quot;supportedLocations&quot;: [ # List of all supported locations. This field is present only if the limit has a {region} or {zone} dimension.
+        &quot;A String&quot;,
+      ],
       &quot;unit&quot;: &quot;A String&quot;, # The limit unit. An example unit would be `1/{project}/{region}` Note that `{project}` and `{region}` are not placeholders in this example; the literal characters `{` and `}` occur in the string.
     },
   ],
@@ -216,6 +219,9 @@ <h3>Method Details</h3>
           },
         },
       ],
+      &quot;supportedLocations&quot;: [ # List of all supported locations. This field is present only if the limit has a {region} or {zone} dimension.
+        &quot;A String&quot;,
+      ],
       &quot;unit&quot;: &quot;A String&quot;, # The limit unit. An example unit would be `1/{project}/{region}` Note that `{project}` and `{region}` are not placeholders in this example; the literal characters `{` and `}` occur in the string.
     },
   ],
@@ -413,6 +419,9 @@ <h3>Method Details</h3>
               },
             },
           ],
+          &quot;supportedLocations&quot;: [ # List of all supported locations. This field is present only if the limit has a {region} or {zone} dimension.
+            &quot;A String&quot;,
+          ],
           &quot;unit&quot;: &quot;A String&quot;, # The limit unit. An example unit would be `1/{project}/{region}` Note that `{project}` and `{region}` are not placeholders in this example; the literal characters `{` and `}` occur in the string.
         },
       ],
@@ -461,6 +470,9 @@ <h3>Method Details</h3>
               },
             },
           ],
+          &quot;supportedLocations&quot;: [ # List of all supported locations. This field is present only if the limit has a {region} or {zone} dimension.
+            &quot;A String&quot;,
+          ],
           &quot;unit&quot;: &quot;A String&quot;, # The limit unit. An example unit would be `1/{project}/{region}` Note that `{project}` and `{region}` are not placeholders in this example; the literal characters `{` and `}` occur in the string.
         },
       ],

docs/dyn/serviceusage_v1beta1.services.consumerQuotaMetrics.limits.html

@@ -159,6 +159,9 @@ <h3>Method Details</h3>
       },
     },
   ],
+  &quot;supportedLocations&quot;: [ # List of all supported locations. This field is present only if the limit has a {region} or {zone} dimension.
+    &quot;A String&quot;,
+  ],
   &quot;unit&quot;: &quot;A String&quot;, # The limit unit. An example unit would be `1/{project}/{region}` Note that `{project}` and `{region}` are not placeholders in this example; the literal characters `{` and `}` occur in the string.
 }</pre>
 </div>

googleapiclient/discovery_cache/documents/serviceusage.v1.json

@@ -426,7 +426,7 @@
       }
     }
   },
-  "revision": "20211207",
+  "revision": "20211215",
   "rootUrl": "https://serviceusage.googleapis.com/",
   "schemas": {
     "AdminQuotaPolicy": {
@@ -845,11 +845,11 @@
       "type": "object"
     },
     "Control": {
-      "description": "Selects and configures the service controller used by the service. The service controller handles features like abuse, quota, billing, logging, monitoring, etc.",
+      "description": "Selects and configures the service controller used by the service. The service controller handles two things: - **What is allowed:** for each API request, Chemist checks the project status, activation status, abuse status, billing status, service status, location restrictions, VPC Service Controls, SuperQuota, and other policies. - **What has happened:** for each API response, Chemist reports the telemetry data to analytics, auditing, billing, eventing, logging, monitoring, sawmill, and tracing. Chemist also accepts telemetry data not associated with API traffic, such as billing metrics. Example: control: environment: servicecontrol.googleapis.com",
       "id": "Control",
       "properties": {
         "environment": {
-          "description": "The service control environment to use. If empty, no control plane feature (like quota and billing) will be enabled.",
+          "description": "The service controller environment to use. If empty, no control plane feature (like quota and billing) will be enabled. The recommended value for most services is servicecontrol.googleapis.com",
           "type": "string"
         }
       },

googleapiclient/discovery_cache/documents/serviceusage.v1beta1.json

@@ -959,7 +959,7 @@
       }
     }
   },
-  "revision": "20211207",
+  "revision": "20211215",
   "rootUrl": "https://serviceusage.googleapis.com/",
   "schemas": {
     "AdminQuotaPolicy": {
@@ -1331,6 +1331,13 @@
           },
           "type": "array"
         },
+        "supportedLocations": {
+          "description": "List of all supported locations. This field is present only if the limit has a {region} or {zone} dimension.",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
         "unit": {
           "description": "The limit unit. An example unit would be `1/{project}/{region}` Note that `{project}` and `{region}` are not placeholders in this example; the literal characters `{` and `}` occur in the string.",
           "type": "string"
@@ -1429,11 +1436,11 @@
       "type": "object"
     },
     "Control": {
-      "description": "Selects and configures the service controller used by the service. The service controller handles features like abuse, quota, billing, logging, monitoring, etc.",
+      "description": "Selects and configures the service controller used by the service. The service controller handles two things: - **What is allowed:** for each API request, Chemist checks the project status, activation status, abuse status, billing status, service status, location restrictions, VPC Service Controls, SuperQuota, and other policies. - **What has happened:** for each API response, Chemist reports the telemetry data to analytics, auditing, billing, eventing, logging, monitoring, sawmill, and tracing. Chemist also accepts telemetry data not associated with API traffic, such as billing metrics. Example: control: environment: servicecontrol.googleapis.com",
       "id": "Control",
       "properties": {
         "environment": {
-          "description": "The service control environment to use. If empty, no control plane feature (like quota and billing) will be enabled.",
+          "description": "The service controller environment to use. If empty, no control plane feature (like quota and billing) will be enabled. The recommended value for most services is servicecontrol.googleapis.com",
           "type": "string"
         }
       },