feat(bigtableadmin): update the api

#### bigtableadmin:v2

The following keys were added:
- schemas.AppProfile.properties.dataBoostIsolationReadOnly.$ref (Total Keys: 1)
- schemas.CheckConsistencyRequest.properties.dataBoostReadLocalWrites.$ref (Total Keys: 1)
- schemas.CheckConsistencyRequest.properties.standardReadRemoteWrites.$ref (Total Keys: 1)
- schemas.ColumnFamily.properties.valueType.$ref (Total Keys: 1)
- schemas.DataBoostIsolationReadOnly (Total Keys: 3)
- schemas.DataBoostReadLocalWrites (Total Keys: 2)
- schemas.GoogleBigtableAdminV2TypeAggregate (Total Keys: 8)
- schemas.GoogleBigtableAdminV2TypeBytes (Total Keys: 8)
- schemas.GoogleBigtableAdminV2TypeInt64 (Total Keys: 9)
- schemas.StandardReadRemoteWrites (Total Keys: 2)
- schemas.Type (Total Keys: 5)

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

@@ -111,6 +111,9 @@ <h3>Method Details</h3>
     The object takes the form of:
 
 { # A configuration object describing how Cloud Bigtable should treat traffic from a particular end user application.
+  &quot;dataBoostIsolationReadOnly&quot;: { # Data Boost is a serverless compute capability that lets you run high-throughput read jobs on your Bigtable data, without impacting the performance of the clusters that handle your application traffic. Currently, Data Boost exclusively supports read-only use-cases with single-cluster routing. Data Boost reads are only guaranteed to see the results of writes that were written at least 30 minutes ago. This means newly written values may not become visible for up to 30m, and also means that old values may remain visible for up to 30m after being deleted or overwritten. To mitigate the staleness of the data, users may either wait 30m, or use CheckConsistency. # Specifies that this app profile is intended for read-only usage via the Data Boost feature.
+    &quot;computeBillingOwner&quot;: &quot;A String&quot;, # The Compute Billing Owner for this Data Boost App Profile.
+  },
   &quot;description&quot;: &quot;A String&quot;, # Long form description of the use case for this AppProfile.
   &quot;etag&quot;: &quot;A String&quot;, # Strongly validated etag for optimistic concurrency control. Preserve the value returned from `GetAppProfile` when calling `UpdateAppProfile` to fail the request if there has been a modification in the mean time. The `update_mask` of the request need not include `etag` for this protection to apply. See [Wikipedia](https://en.wikipedia.org/wiki/HTTP_ETag) and [RFC 7232](https://tools.ietf.org/html/rfc7232#section-2.3) for more details.
   &quot;multiClusterRoutingUseAny&quot;: { # Read/write requests are routed to the nearest cluster in the instance, and will fail over to the nearest cluster that is available in the event of transient errors or delays. Clusters in a region are considered equidistant. Choosing this option sacrifices read-your-writes consistency to improve availability. # Use a multi-cluster routing policy.
@@ -140,6 +143,9 @@ <h3>Method Details</h3>
   An object of the form:
 
     { # A configuration object describing how Cloud Bigtable should treat traffic from a particular end user application.
+  &quot;dataBoostIsolationReadOnly&quot;: { # Data Boost is a serverless compute capability that lets you run high-throughput read jobs on your Bigtable data, without impacting the performance of the clusters that handle your application traffic. Currently, Data Boost exclusively supports read-only use-cases with single-cluster routing. Data Boost reads are only guaranteed to see the results of writes that were written at least 30 minutes ago. This means newly written values may not become visible for up to 30m, and also means that old values may remain visible for up to 30m after being deleted or overwritten. To mitigate the staleness of the data, users may either wait 30m, or use CheckConsistency. # Specifies that this app profile is intended for read-only usage via the Data Boost feature.
+    &quot;computeBillingOwner&quot;: &quot;A String&quot;, # The Compute Billing Owner for this Data Boost App Profile.
+  },
   &quot;description&quot;: &quot;A String&quot;, # Long form description of the use case for this AppProfile.
   &quot;etag&quot;: &quot;A String&quot;, # Strongly validated etag for optimistic concurrency control. Preserve the value returned from `GetAppProfile` when calling `UpdateAppProfile` to fail the request if there has been a modification in the mean time. The `update_mask` of the request need not include `etag` for this protection to apply. See [Wikipedia](https://en.wikipedia.org/wiki/HTTP_ETag) and [RFC 7232](https://tools.ietf.org/html/rfc7232#section-2.3) for more details.
   &quot;multiClusterRoutingUseAny&quot;: { # Read/write requests are routed to the nearest cluster in the instance, and will fail over to the nearest cluster that is available in the event of transient errors or delays. Clusters in a region are considered equidistant. Choosing this option sacrifices read-your-writes consistency to improve availability. # Use a multi-cluster routing policy.
@@ -193,6 +199,9 @@ <h3>Method Details</h3>
   An object of the form:
 
     { # A configuration object describing how Cloud Bigtable should treat traffic from a particular end user application.
+  &quot;dataBoostIsolationReadOnly&quot;: { # Data Boost is a serverless compute capability that lets you run high-throughput read jobs on your Bigtable data, without impacting the performance of the clusters that handle your application traffic. Currently, Data Boost exclusively supports read-only use-cases with single-cluster routing. Data Boost reads are only guaranteed to see the results of writes that were written at least 30 minutes ago. This means newly written values may not become visible for up to 30m, and also means that old values may remain visible for up to 30m after being deleted or overwritten. To mitigate the staleness of the data, users may either wait 30m, or use CheckConsistency. # Specifies that this app profile is intended for read-only usage via the Data Boost feature.
+    &quot;computeBillingOwner&quot;: &quot;A String&quot;, # The Compute Billing Owner for this Data Boost App Profile.
+  },
   &quot;description&quot;: &quot;A String&quot;, # Long form description of the use case for this AppProfile.
   &quot;etag&quot;: &quot;A String&quot;, # Strongly validated etag for optimistic concurrency control. Preserve the value returned from `GetAppProfile` when calling `UpdateAppProfile` to fail the request if there has been a modification in the mean time. The `update_mask` of the request need not include `etag` for this protection to apply. See [Wikipedia](https://en.wikipedia.org/wiki/HTTP_ETag) and [RFC 7232](https://tools.ietf.org/html/rfc7232#section-2.3) for more details.
   &quot;multiClusterRoutingUseAny&quot;: { # Read/write requests are routed to the nearest cluster in the instance, and will fail over to the nearest cluster that is available in the event of transient errors or delays. Clusters in a region are considered equidistant. Choosing this option sacrifices read-your-writes consistency to improve availability. # Use a multi-cluster routing policy.
@@ -231,6 +240,9 @@ <h3>Method Details</h3>
     { # Response message for BigtableInstanceAdmin.ListAppProfiles.
   &quot;appProfiles&quot;: [ # The list of requested app profiles.
     { # A configuration object describing how Cloud Bigtable should treat traffic from a particular end user application.
+      &quot;dataBoostIsolationReadOnly&quot;: { # Data Boost is a serverless compute capability that lets you run high-throughput read jobs on your Bigtable data, without impacting the performance of the clusters that handle your application traffic. Currently, Data Boost exclusively supports read-only use-cases with single-cluster routing. Data Boost reads are only guaranteed to see the results of writes that were written at least 30 minutes ago. This means newly written values may not become visible for up to 30m, and also means that old values may remain visible for up to 30m after being deleted or overwritten. To mitigate the staleness of the data, users may either wait 30m, or use CheckConsistency. # Specifies that this app profile is intended for read-only usage via the Data Boost feature.
+        &quot;computeBillingOwner&quot;: &quot;A String&quot;, # The Compute Billing Owner for this Data Boost App Profile.
+      },
       &quot;description&quot;: &quot;A String&quot;, # Long form description of the use case for this AppProfile.
       &quot;etag&quot;: &quot;A String&quot;, # Strongly validated etag for optimistic concurrency control. Preserve the value returned from `GetAppProfile` when calling `UpdateAppProfile` to fail the request if there has been a modification in the mean time. The `update_mask` of the request need not include `etag` for this protection to apply. See [Wikipedia](https://en.wikipedia.org/wiki/HTTP_ETag) and [RFC 7232](https://tools.ietf.org/html/rfc7232#section-2.3) for more details.
       &quot;multiClusterRoutingUseAny&quot;: { # Read/write requests are routed to the nearest cluster in the instance, and will fail over to the nearest cluster that is available in the event of transient errors or delays. Clusters in a region are considered equidistant. Choosing this option sacrifices read-your-writes consistency to improve availability. # Use a multi-cluster routing policy.
@@ -280,6 +292,9 @@ <h3>Method Details</h3>
     The object takes the form of:
 
 { # A configuration object describing how Cloud Bigtable should treat traffic from a particular end user application.
+  &quot;dataBoostIsolationReadOnly&quot;: { # Data Boost is a serverless compute capability that lets you run high-throughput read jobs on your Bigtable data, without impacting the performance of the clusters that handle your application traffic. Currently, Data Boost exclusively supports read-only use-cases with single-cluster routing. Data Boost reads are only guaranteed to see the results of writes that were written at least 30 minutes ago. This means newly written values may not become visible for up to 30m, and also means that old values may remain visible for up to 30m after being deleted or overwritten. To mitigate the staleness of the data, users may either wait 30m, or use CheckConsistency. # Specifies that this app profile is intended for read-only usage via the Data Boost feature.
+    &quot;computeBillingOwner&quot;: &quot;A String&quot;, # The Compute Billing Owner for this Data Boost App Profile.
+  },
   &quot;description&quot;: &quot;A String&quot;, # Long form description of the use case for this AppProfile.
   &quot;etag&quot;: &quot;A String&quot;, # Strongly validated etag for optimistic concurrency control. Preserve the value returned from `GetAppProfile` when calling `UpdateAppProfile` to fail the request if there has been a modification in the mean time. The `update_mask` of the request need not include `etag` for this protection to apply. See [Wikipedia](https://en.wikipedia.org/wiki/HTTP_ETag) and [RFC 7232](https://tools.ietf.org/html/rfc7232#section-2.3) for more details.
   &quot;multiClusterRoutingUseAny&quot;: { # Read/write requests are routed to the nearest cluster in the instance, and will fail over to the nearest cluster that is available in the event of transient errors or delays. Clusters in a region are considered equidistant. Choosing this option sacrifices read-your-writes consistency to improve availability. # Use a multi-cluster routing policy.