chore: regenerate serviceusage client (googleapis#22503)

Generated in GitHub action: https://togithub.com/googleapis/googleapis/google-api-java-client-services/actions/workflows/codegen.yaml

Author: yoshi-code-bot

clients/google-api-services-serviceusage/v1/2.0.0/README.md

@@ -22,7 +22,7 @@ Add the following lines to your `pom.xml` file:
     <dependency>
       <groupId>com.google.apis</groupId>
       <artifactId>google-api-services-serviceusage</artifactId>
-      <version>v1-rev20240707-2.0.0</version>
+      <version>v1-rev20240712-2.0.0</version>
     </dependency>
   </dependencies>
 </project>
@@ -35,7 +35,7 @@ repositories {
   mavenCentral()
 }
 dependencies {
-  implementation 'com.google.apis:google-api-services-serviceusage:v1-rev20240707-2.0.0'
+  implementation 'com.google.apis:google-api-services-serviceusage:v1-rev20240712-2.0.0'
 }
 ```
 

clients/google-api-services-serviceusage/v1/2.0.0/com/google/api/services/serviceusage/v1/model/ContextRule.java

@@ -46,14 +46,16 @@ public final class ContextRule extends com.google.api.client.json.GenericJson {
   private java.util.List<java.lang.String> allowedResponseExtensions;
 
   /**
-   * A list of full type names of provided contexts.
+   * A list of full type names of provided contexts. It is used to support propagating HTTP headers
+   * and ETags from the response extension.
    * The value may be {@code null}.
    */
   @com.google.api.client.util.Key
   private java.util.List<java.lang.String> provided;
 
   /**
-   * A list of full type names of requested contexts.
+   * A list of full type names of requested contexts, only the requested context will be made
+   * available to the backend.
    * The value may be {@code null}.
    */
   @com.google.api.client.util.Key
@@ -105,15 +107,17 @@ public ContextRule setAllowedResponseExtensions(java.util.List<java.lang.String>
   }
 
   /**
-   * A list of full type names of provided contexts.
+   * A list of full type names of provided contexts. It is used to support propagating HTTP headers
+   * and ETags from the response extension.
    * @return value or {@code null} for none
    */
   public java.util.List<java.lang.String> getProvided() {
     return provided;
   }
 
   /**
-   * A list of full type names of provided contexts.
+   * A list of full type names of provided contexts. It is used to support propagating HTTP headers
+   * and ETags from the response extension.
    * @param provided provided or {@code null} for none
    */
   public ContextRule setProvided(java.util.List<java.lang.String> provided) {
@@ -122,15 +126,17 @@ public ContextRule setProvided(java.util.List<java.lang.String> provided) {
   }
 
   /**
-   * A list of full type names of requested contexts.
+   * A list of full type names of requested contexts, only the requested context will be made
+   * available to the backend.
    * @return value or {@code null} for none
    */
   public java.util.List<java.lang.String> getRequested() {
     return requested;
   }
 
   /**
-   * A list of full type names of requested contexts.
+   * A list of full type names of requested contexts, only the requested context will be made
+   * available to the backend.
    * @param requested requested or {@code null} for none
    */
   public ContextRule setRequested(java.util.List<java.lang.String> requested) {

clients/google-api-services-serviceusage/v1/2.0.0/com/google/api/services/serviceusage/v1/model/Documentation.java

@@ -22,24 +22,21 @@
  * Overview content: (== include google/foo/overview.md ==) - name: Tutorial content: (== include
  * google/foo/tutorial.md ==) subpages: - name: Java content: (== include
  * google/foo/tutorial_java.md ==) rules: - selector: google.calendar.Calendar.Get description: >
- * ... - selector: google.calendar.Calendar.Put description: > ... code_snippet_rules: - selector:
- * google.calendar.Calendar.Delete code_snippets: - includes: - github_include: region_tag:
- * calendar_delete code_language: JAVA account: GoogleCloudPlatform project: java-docs-samples file:
- * calendar/delete.java Documentation is provided in markdown syntax. In addition to standard
- * markdown features, definition lists, tables and fenced code blocks are supported. Section headers
- * can be provided and are interpreted relative to the section nesting of the context where a
- * documentation fragment is embedded. Documentation from the IDL is merged with documentation
- * defined via the config at normalization time, where documentation provided by config rules
- * overrides IDL provided. A number of constructs specific to the API platform are supported in
- * documentation text. In order to reference a proto element, the following notation can be used:
- * [fully.qualified.proto.name][] To override the display text used for the link, this can be used:
- * [display text][fully.qualified.proto.name] Text can be excluded from doc using the following
- * notation: (-- internal comment --) A few directives are available in documentation. Note that
- * directives must appear on a single line to be properly identified. The `include` directive
- * includes a markdown file from an external source: (== include path/to/file ==) The `resource_for`
- * directive marks a message to be the resource of a collection in REST view. If it is not
- * specified, tools attempt to infer the resource from the operations in a collection: (==
- * resource_for v1.shelves.books ==) The directive `suppress_warning` does not directly affect
+ * ... - selector: google.calendar.Calendar.Put description: > ... Documentation is provided in
+ * markdown syntax. In addition to standard markdown features, definition lists, tables and fenced
+ * code blocks are supported. Section headers can be provided and are interpreted relative to the
+ * section nesting of the context where a documentation fragment is embedded. Documentation from the
+ * IDL is merged with documentation defined via the config at normalization time, where
+ * documentation provided by config rules overrides IDL provided. A number of constructs specific to
+ * the API platform are supported in documentation text. In order to reference a proto element, the
+ * following notation can be used: [fully.qualified.proto.name][] To override the display text used
+ * for the link, this can be used: [display text][fully.qualified.proto.name] Text can be excluded
+ * from doc using the following notation: (-- internal comment --) A few directives are available in
+ * documentation. Note that directives must appear on a single line to be properly identified. The
+ * `include` directive includes a markdown file from an external source: (== include path/to/file
+ * ==) The `resource_for` directive marks a message to be the resource of a collection in REST view.
+ * If it is not specified, tools attempt to infer the resource from the operations in a collection:
+ * (== resource_for v1.shelves.books ==) The directive `suppress_warning` does not directly affect
  * documentation and is documented together with service config validation.
  *
  * <p> This is the Java data model class that specifies how to parse/serialize into the JSON that is

clients/google-api-services-serviceusage/v1/2.0.0/com/google/api/services/serviceusage/v1/model/HttpRule.java

@@ -105,23 +105,24 @@
  * this by specifying a `HttpRule` that maps the gRPC method to a REST endpoint, achieving the same
  * effect as the proto annotation. This can be particularly useful if you have a proto that is
  * reused in multiple services. Note that any transcoding specified in the service config will
- * override any matching transcoding configuration in the proto. Example below selects a gRPC method
- * and applies HttpRule to it. http: rules: - selector: example.v1.Messaging.GetMessage get:
- * /v1/messages/{message_id}/{sub.subfield} Special notes When gRPC Transcoding is used to map a
- * gRPC to JSON REST endpoints, the proto to JSON conversion must follow the [proto3
- * specification](https://developers.google.com/protocol-buffers/docs/proto3#json). While the single
- * segment variable follows the semantics of [RFC 6570](https://tools.ietf.org/html/rfc6570) Section
- * 3.2.2 Simple String Expansion, the multi segment variable **does not** follow RFC 6570 Section
- * 3.2.3 Reserved Expansion. The reason is that the Reserved Expansion does not expand special
- * characters like `?` and `#`, which would lead to invalid URLs. As the result, gRPC Transcoding
- * uses a custom encoding for multi segment variables. The path variables **must not** refer to any
- * repeated or mapped field, because client libraries are not capable of handling such variable
- * expansion. The path variables **must not** capture the leading "/" character. The reason is that
- * the most common use case "{var}" does not capture the leading "/" character. For consistency, all
- * path variables must share the same behavior. Repeated message fields must not be mapped to URL
- * query parameters, because no client library can support such complicated mapping. If an API needs
- * to use a JSON array for request or response body, it can map the request or response body to a
- * repeated field. However, some gRPC Transcoding implementations may not support this feature.
+ * override any matching transcoding configuration in the proto. The following example selects a
+ * gRPC method and applies an `HttpRule` to it: http: rules: - selector:
+ * example.v1.Messaging.GetMessage get: /v1/messages/{message_id}/{sub.subfield} Special notes When
+ * gRPC Transcoding is used to map a gRPC to JSON REST endpoints, the proto to JSON conversion must
+ * follow the [proto3 specification](https://developers.google.com/protocol-
+ * buffers/docs/proto3#json). While the single segment variable follows the semantics of [RFC
+ * 6570](https://tools.ietf.org/html/rfc6570) Section 3.2.2 Simple String Expansion, the multi
+ * segment variable **does not** follow RFC 6570 Section 3.2.3 Reserved Expansion. The reason is
+ * that the Reserved Expansion does not expand special characters like `?` and `#`, which would lead
+ * to invalid URLs. As the result, gRPC Transcoding uses a custom encoding for multi segment
+ * variables. The path variables **must not** refer to any repeated or mapped field, because client
+ * libraries are not capable of handling such variable expansion. The path variables **must not**
+ * capture the leading "/" character. The reason is that the most common use case "{var}" does not
+ * capture the leading "/" character. For consistency, all path variables must share the same
+ * behavior. Repeated message fields must not be mapped to URL query parameters, because no client
+ * library can support such complicated mapping. If an API needs to use a JSON array for request or
+ * response body, it can map the request or response body to a repeated field. However, some gRPC
+ * Transcoding implementations may not support this feature.
  *
  * <p> This is the Java data model class that specifies how to parse/serialize into the JSON that is
  * transmitted over HTTP when working with the Service Usage API. For a detailed explanation see:

clients/google-api-services-serviceusage/v1/2.0.0/pom.xml

@@ -8,8 +8,8 @@
 
   <groupId>com.google.apis</groupId>
   <artifactId>google-api-services-serviceusage</artifactId>
-  <version>v1-rev20240707-2.0.0</version>
-  <name>Service Usage API v1-rev20240707-2.0.0</name>
+  <version>v1-rev20240712-2.0.0</version>
+  <name>Service Usage API v1-rev20240712-2.0.0</name>
   <packaging>jar</packaging>
 
   <inceptionYear>2011</inceptionYear>

clients/google-api-services-serviceusage/v1/README.md

@@ -22,7 +22,7 @@ Add the following lines to your `pom.xml` file:
     <dependency>
       <groupId>com.google.apis</groupId>
       <artifactId>google-api-services-serviceusage</artifactId>
-      <version>v1-rev20240707-2.0.0</version>
+      <version>v1-rev20240712-2.0.0</version>
     </dependency>
   </dependencies>
 </project>
@@ -35,7 +35,7 @@ repositories {
   mavenCentral()
 }
 dependencies {
-  implementation 'com.google.apis:google-api-services-serviceusage:v1-rev20240707-2.0.0'
+  implementation 'com.google.apis:google-api-services-serviceusage:v1-rev20240712-2.0.0'
 }
 ```
 

clients/google-api-services-serviceusage/v1beta1/2.0.0/README.md

@@ -22,7 +22,7 @@ Add the following lines to your `pom.xml` file:
     <dependency>
       <groupId>com.google.apis</groupId>
       <artifactId>google-api-services-serviceusage</artifactId>
-      <version>v1beta1-rev20240707-2.0.0</version>
+      <version>v1beta1-rev20240712-2.0.0</version>
     </dependency>
   </dependencies>
 </project>
@@ -35,7 +35,7 @@ repositories {
   mavenCentral()
 }
 dependencies {
-  implementation 'com.google.apis:google-api-services-serviceusage:v1beta1-rev20240707-2.0.0'
+  implementation 'com.google.apis:google-api-services-serviceusage:v1beta1-rev20240712-2.0.0'
 }
 ```
 

clients/google-api-services-serviceusage/v1beta1/2.0.0/com/google/api/services/serviceusage/v1beta1/model/ContextRule.java

@@ -46,14 +46,16 @@ public final class ContextRule extends com.google.api.client.json.GenericJson {
   private java.util.List<java.lang.String> allowedResponseExtensions;
 
   /**
-   * A list of full type names of provided contexts.
+   * A list of full type names of provided contexts. It is used to support propagating HTTP headers
+   * and ETags from the response extension.
    * The value may be {@code null}.
    */
   @com.google.api.client.util.Key
   private java.util.List<java.lang.String> provided;
 
   /**
-   * A list of full type names of requested contexts.
+   * A list of full type names of requested contexts, only the requested context will be made
+   * available to the backend.
    * The value may be {@code null}.
    */
   @com.google.api.client.util.Key
@@ -105,15 +107,17 @@ public ContextRule setAllowedResponseExtensions(java.util.List<java.lang.String>
   }
 
   /**
-   * A list of full type names of provided contexts.
+   * A list of full type names of provided contexts. It is used to support propagating HTTP headers
+   * and ETags from the response extension.
    * @return value or {@code null} for none
    */
   public java.util.List<java.lang.String> getProvided() {
     return provided;
   }
 
   /**
-   * A list of full type names of provided contexts.
+   * A list of full type names of provided contexts. It is used to support propagating HTTP headers
+   * and ETags from the response extension.
    * @param provided provided or {@code null} for none
    */
   public ContextRule setProvided(java.util.List<java.lang.String> provided) {
@@ -122,15 +126,17 @@ public ContextRule setProvided(java.util.List<java.lang.String> provided) {
   }
 
   /**
-   * A list of full type names of requested contexts.
+   * A list of full type names of requested contexts, only the requested context will be made
+   * available to the backend.
    * @return value or {@code null} for none
    */
   public java.util.List<java.lang.String> getRequested() {
     return requested;
   }
 
   /**
-   * A list of full type names of requested contexts.
+   * A list of full type names of requested contexts, only the requested context will be made
+   * available to the backend.
    * @param requested requested or {@code null} for none
    */
   public ContextRule setRequested(java.util.List<java.lang.String> requested) {

clients/google-api-services-serviceusage/v1beta1/2.0.0/com/google/api/services/serviceusage/v1beta1/model/Documentation.java

@@ -22,24 +22,21 @@
  * Overview content: (== include google/foo/overview.md ==) - name: Tutorial content: (== include
  * google/foo/tutorial.md ==) subpages: - name: Java content: (== include
  * google/foo/tutorial_java.md ==) rules: - selector: google.calendar.Calendar.Get description: >
- * ... - selector: google.calendar.Calendar.Put description: > ... code_snippet_rules: - selector:
- * google.calendar.Calendar.Delete code_snippets: - includes: - github_include: region_tag:
- * calendar_delete code_language: JAVA account: GoogleCloudPlatform project: java-docs-samples file:
- * calendar/delete.java Documentation is provided in markdown syntax. In addition to standard
- * markdown features, definition lists, tables and fenced code blocks are supported. Section headers
- * can be provided and are interpreted relative to the section nesting of the context where a
- * documentation fragment is embedded. Documentation from the IDL is merged with documentation
- * defined via the config at normalization time, where documentation provided by config rules
- * overrides IDL provided. A number of constructs specific to the API platform are supported in
- * documentation text. In order to reference a proto element, the following notation can be used:
- * [fully.qualified.proto.name][] To override the display text used for the link, this can be used:
- * [display text][fully.qualified.proto.name] Text can be excluded from doc using the following
- * notation: (-- internal comment --) A few directives are available in documentation. Note that
- * directives must appear on a single line to be properly identified. The `include` directive
- * includes a markdown file from an external source: (== include path/to/file ==) The `resource_for`
- * directive marks a message to be the resource of a collection in REST view. If it is not
- * specified, tools attempt to infer the resource from the operations in a collection: (==
- * resource_for v1.shelves.books ==) The directive `suppress_warning` does not directly affect
+ * ... - selector: google.calendar.Calendar.Put description: > ... Documentation is provided in
+ * markdown syntax. In addition to standard markdown features, definition lists, tables and fenced
+ * code blocks are supported. Section headers can be provided and are interpreted relative to the
+ * section nesting of the context where a documentation fragment is embedded. Documentation from the
+ * IDL is merged with documentation defined via the config at normalization time, where
+ * documentation provided by config rules overrides IDL provided. A number of constructs specific to
+ * the API platform are supported in documentation text. In order to reference a proto element, the
+ * following notation can be used: [fully.qualified.proto.name][] To override the display text used
+ * for the link, this can be used: [display text][fully.qualified.proto.name] Text can be excluded
+ * from doc using the following notation: (-- internal comment --) A few directives are available in
+ * documentation. Note that directives must appear on a single line to be properly identified. The
+ * `include` directive includes a markdown file from an external source: (== include path/to/file
+ * ==) The `resource_for` directive marks a message to be the resource of a collection in REST view.
+ * If it is not specified, tools attempt to infer the resource from the operations in a collection:
+ * (== resource_for v1.shelves.books ==) The directive `suppress_warning` does not directly affect
  * documentation and is documented together with service config validation.
  *
  * <p> This is the Java data model class that specifies how to parse/serialize into the JSON that is