chore: regenerate bigtableadmin client (googleapis#22361)

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

clients/google-api-services-bigtableadmin/v2/2.0.0/com/google/api/services/bigtableadmin/v2/model/GoogleBigtableAdminV2TypeBytesEncodingRaw.java

@@ -17,7 +17,7 @@
 package com.google.api.services.bigtableadmin.v2.model;
 
 /**
- * Leaves the value "as-is" * Natural sort? Yes * Self-delimiting? No * Compatibility? N/A
+ * Leaves the value "as-is" * Order-preserving? Yes * Self-delimiting? No * Compatibility? N/A
  *
  * <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 Cloud Bigtable Admin API. For a detailed explanation

clients/google-api-services-bigtableadmin/v2/2.0.0/com/google/api/services/bigtableadmin/v2/model/GoogleBigtableAdminV2TypeInt64EncodingBigEndianBytes.java

@@ -17,7 +17,7 @@
 package com.google.api.services.bigtableadmin.v2.model;
 
 /**
- * Encodes the value as an 8-byte big endian twos complement `Bytes` value. * Natural sort? No
+ * Encodes the value as an 8-byte big endian twos complement `Bytes` value. * Order-preserving? No
  * (positive values only) * Self-delimiting? Yes * Compatibility? - BigQuery Federation `BINARY`
  * encoding - HBase `Bytes.toBytes` - Java `ByteBuffer.putLong()` with `ByteOrder.BIG_ENDIAN`
  *
@@ -33,22 +33,22 @@
 public final class GoogleBigtableAdminV2TypeInt64EncodingBigEndianBytes extends com.google.api.client.json.GenericJson {
 
   /**
-   * The underlying `Bytes` type, which may be able to encode further.
+   * Deprecated: ignored if set.
    * The value may be {@code null}.
    */
   @com.google.api.client.util.Key
   private GoogleBigtableAdminV2TypeBytes bytesType;
 
   /**
-   * The underlying `Bytes` type, which may be able to encode further.
+   * Deprecated: ignored if set.
    * @return value or {@code null} for none
    */
   public GoogleBigtableAdminV2TypeBytes getBytesType() {
     return bytesType;
   }
 
   /**
-   * The underlying `Bytes` type, which may be able to encode further.
+   * Deprecated: ignored if set.
    * @param bytesType bytesType or {@code null} for none
    */
   public GoogleBigtableAdminV2TypeInt64EncodingBigEndianBytes setBytesType(GoogleBigtableAdminV2TypeBytes bytesType) {

clients/google-api-services-bigtableadmin/v2/2.0.0/com/google/api/services/bigtableadmin/v2/model/Type.java

@@ -20,22 +20,18 @@
  * `Type` represents the type of data that is written to, read from, or stored in Bigtable. It is
  * heavily based on the GoogleSQL standard to help maintain familiarity and consistency across
  * products and features. For compatibility with Bigtable's existing untyped APIs, each `Type`
- * includes an `Encoding` which describes how to convert to/from the underlying data. This might
- * involve composing a series of steps into an "encoding chain," for example to convert from INT64
- * -> STRING -> raw bytes. In most cases, a "link" in the encoding chain will be based an on
- * existing GoogleSQL conversion function like `CAST`. Each link in the encoding chain also defines
- * the following properties: * Natural sort: Does the encoded value sort consistently with the
- * original typed value? Note that Bigtable will always sort data based on the raw encoded value,
- * *not* the decoded type. - Example: BYTES values sort in the same order as their raw encodings. -
- * Counterexample: Encoding INT64 to a fixed-width STRING does *not* preserve sort order when
- * dealing with negative numbers. INT64(1) > INT64(-1), but STRING("-00001") > STRING("00001). - The
- * overall encoding chain has this property if *every* link does. * Self-delimiting: If we
- * concatenate two encoded values, can we always tell where the first one ends and the second one
- * begins? - Example: If we encode INT64s to fixed-width STRINGs, the first value will always
- * contain exactly N digits, possibly preceded by a sign. - Counterexample: If we concatenate two
- * UTF-8 encoded STRINGs, we have no way to tell where the first one ends. - The overall encoding
- * chain has this property if *any* link does. * Compatibility: Which other systems have matching
- * encoding schemes? For example, does this encoding have a GoogleSQL equivalent? HBase? Java?
+ * includes an `Encoding` which describes how to convert to/from the underlying data. Each encoding
+ * also defines the following properties: * Order-preserving: Does the encoded value sort
+ * consistently with the original typed value? Note that Bigtable will always sort data based on the
+ * raw encoded value, *not* the decoded type. - Example: BYTES values sort in the same order as
+ * their raw encodings. - Counterexample: Encoding INT64 as a fixed-width decimal string does *not*
+ * preserve sort order when dealing with negative numbers. INT64(1) > INT64(-1), but
+ * STRING("-00001") > STRING("00001). * Self-delimiting: If we concatenate two encoded values, can
+ * we always tell where the first one ends and the second one begins? - Example: If we encode INT64s
+ * to fixed-width STRINGs, the first value will always contain exactly N digits, possibly preceded
+ * by a sign. - Counterexample: If we concatenate two UTF-8 encoded STRINGs, we have no way to tell
+ * where the first one ends. * Compatibility: Which other systems have matching encoding schemes?
+ * For example, does this encoding have a GoogleSQL equivalent? HBase? Java?
  *
  * <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 Cloud Bigtable Admin API. For a detailed explanation

clients/google-api-services-bigtableadmin/v2/2.0.0/pom.xml

@@ -8,8 +8,8 @@
 
   <groupId>com.google.apis</groupId>
   <artifactId>google-api-services-bigtableadmin</artifactId>
-  <version>v2-rev20240604-2.0.0</version>
-  <name>Cloud Bigtable Admin API v2-rev20240604-2.0.0</name>
+  <version>v2-rev20240628-2.0.0</version>
+  <name>Cloud Bigtable Admin API v2-rev20240628-2.0.0</name>
   <packaging>jar</packaging>
 
   <inceptionYear>2011</inceptionYear>

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