chore: regenerate serviceconsumermanagement client (googleapis#22437)

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-serviceconsumermanagement/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-serviceconsumermanagement</artifactId>
-      <version>v1-rev20240602-2.0.0</version>
+      <version>v1-rev20240707-2.0.0</version>
     </dependency>
   </dependencies>
 </project>
@@ -35,7 +35,7 @@ repositories {
   mavenCentral()
 }
 dependencies {
-  implementation 'com.google.apis:google-api-services-serviceconsumermanagement:v1-rev20240602-2.0.0'
+  implementation 'com.google.apis:google-api-services-serviceconsumermanagement:v1-rev20240707-2.0.0'
 }
 ```
 

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

@@ -22,21 +22,24 @@
  * 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: > ... 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: > ... 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
  * 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-serviceconsumermanagement/v1/2.0.0/pom.xml

@@ -8,8 +8,8 @@
 
   <groupId>com.google.apis</groupId>
   <artifactId>google-api-services-serviceconsumermanagement</artifactId>
-  <version>v1-rev20240602-2.0.0</version>
-  <name>Service Consumer Management API v1-rev20240602-2.0.0</name>
+  <version>v1-rev20240707-2.0.0</version>
+  <name>Service Consumer Management API v1-rev20240707-2.0.0</name>
   <packaging>jar</packaging>
 
   <inceptionYear>2011</inceptionYear>

clients/google-api-services-serviceconsumermanagement/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-serviceconsumermanagement</artifactId>
-      <version>v1-rev20240602-2.0.0</version>
+      <version>v1-rev20240707-2.0.0</version>
     </dependency>
   </dependencies>
 </project>
@@ -35,7 +35,7 @@ repositories {
   mavenCentral()
 }
 dependencies {
-  implementation 'com.google.apis:google-api-services-serviceconsumermanagement:v1-rev20240602-2.0.0'
+  implementation 'com.google.apis:google-api-services-serviceconsumermanagement:v1-rev20240707-2.0.0'
 }
 ```
 

clients/google-api-services-serviceconsumermanagement/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-serviceconsumermanagement</artifactId>
-      <version>v1beta1-rev20240609-2.0.0</version>
+      <version>v1beta1-rev20240707-2.0.0</version>
     </dependency>
   </dependencies>
 </project>
@@ -35,7 +35,7 @@ repositories {
   mavenCentral()
 }
 dependencies {
-  implementation 'com.google.apis:google-api-services-serviceconsumermanagement:v1beta1-rev20240609-2.0.0'
+  implementation 'com.google.apis:google-api-services-serviceconsumermanagement:v1beta1-rev20240707-2.0.0'
 }
 ```
 

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

@@ -22,21 +22,24 @@
  * 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: > ... 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: > ... 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
  * 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-serviceconsumermanagement/v1beta1/2.0.0/pom.xml

@@ -8,8 +8,8 @@
 
   <groupId>com.google.apis</groupId>
   <artifactId>google-api-services-serviceconsumermanagement</artifactId>
-  <version>v1beta1-rev20240609-2.0.0</version>
-  <name>Service Consumer Management API v1beta1-rev20240609-2.0.0</name>
+  <version>v1beta1-rev20240707-2.0.0</version>
+  <name>Service Consumer Management API v1beta1-rev20240707-2.0.0</name>
   <packaging>jar</packaging>
 
   <inceptionYear>2011</inceptionYear>

clients/google-api-services-serviceconsumermanagement/v1beta1/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-serviceconsumermanagement</artifactId>
-      <version>v1beta1-rev20240609-2.0.0</version>
+      <version>v1beta1-rev20240707-2.0.0</version>
     </dependency>
   </dependencies>
 </project>
@@ -35,7 +35,7 @@ repositories {
   mavenCentral()
 }
 dependencies {
-  implementation 'com.google.apis:google-api-services-serviceconsumermanagement:v1beta1-rev20240609-2.0.0'
+  implementation 'com.google.apis:google-api-services-serviceconsumermanagement:v1beta1-rev20240707-2.0.0'
 }
 ```