chore: Update discovery artifacts (#2517)

## Deleted keys were detected in the following stable discovery artifacts:
accesscontextmanager v1 https://github.com/googleapis/google-api-python-client/commit/bd3d8f58e06ff1818cfcaabe737f24b267957bda
compute v1 https://github.com/googleapis/google-api-python-client/commit/0ec6e073ae8625a0f61b5eb80c718697b53db589
discoveryengine v1 https://github.com/googleapis/google-api-python-client/commit/376be8fa5e44c5a17cfb47bb39c9db7d56ee0f96

## Deleted keys were detected in the following pre-stable discovery artifacts:
compute alpha https://github.com/googleapis/google-api-python-client/commit/0ec6e073ae8625a0f61b5eb80c718697b53db589
compute beta https://github.com/googleapis/google-api-python-client/commit/0ec6e073ae8625a0f61b5eb80c718697b53db589
discoveryengine v1alpha https://github.com/googleapis/google-api-python-client/commit/376be8fa5e44c5a17cfb47bb39c9db7d56ee0f96
discoveryengine v1beta https://github.com/googleapis/google-api-python-client/commit/376be8fa5e44c5a17cfb47bb39c9db7d56ee0f96

## Discovery Artifact Change Summary:
feat(accesscontextmanager): update the api https://github.com/googleapis/google-api-python-client/commit/bd3d8f58e06ff1818cfcaabe737f24b267957bda
feat(calendar): update the api https://github.com/googleapis/google-api-python-client/commit/2d88d4f0289f024b74eb818c41fb7035304db644
feat(chat): update the api https://github.com/googleapis/google-api-python-client/commit/f7ba9138589bfc5506baa73000b1bc82991137e6
feat(cloudchannel): update the api https://github.com/googleapis/google-api-python-client/commit/3fd0d738d8fd6f9d26d8745db368d8084e51961c
feat(compute): update the api https://github.com/googleapis/google-api-python-client/commit/0ec6e073ae8625a0f61b5eb80c718697b53db589
feat(container): update the api https://github.com/googleapis/google-api-python-client/commit/8e4181d9b59aeb0ff11abba589f879fb518f82e0
feat(dataplex): update the api https://github.com/googleapis/google-api-python-client/commit/b571016dc4da99857a165c568e5b4a4ded0c1927
feat(deploymentmanager): update the api https://github.com/googleapis/google-api-python-client/commit/144b3d1267bcbebbf5b02bfaabab6e61e2275b39
feat(discoveryengine): update the api https://github.com/googleapis/google-api-python-client/commit/376be8fa5e44c5a17cfb47bb39c9db7d56ee0f96
feat(fcm): update the api https://github.com/googleapis/google-api-python-client/commit/9e9582ed637921a4aa940a8b0be5e954c0c00014
feat(firebaseml): update the api https://github.com/googleapis/google-api-python-client/commit/df6252a136e13208cde77f3f995bd2a57604f67a
feat(integrations): update the api https://github.com/googleapis/google-api-python-client/commit/1acf476cf9d502121e2ddae91fd37417f49b2adf
feat(networkconnectivity): update the api https://github.com/googleapis/google-api-python-client/commit/af889b96e5759f0a717c6545ccd59dd72677742d
feat(paymentsresellersubscription): update the api https://github.com/googleapis/google-api-python-client/commit/d657753268322ec16e9b39afabc9a74a99a74d40
feat(places): update the api https://github.com/googleapis/google-api-python-client/commit/1a93219dbc646d0a533aa7b20c5649234062a40f
feat(searchads360): update the api https://github.com/googleapis/google-api-python-client/commit/40e2bc76890f991c55e29dbc619fb46bb140e1b3
feat(servicenetworking): update the api https://github.com/googleapis/google-api-python-client/commit/7cc693dbd4bed3d6d790509eba3f7756602388ec
feat(testing): update the api https://github.com/googleapis/google-api-python-client/commit/6158b31cccba3c3e78046a15cd96bf71f1688b49

Author: yoshi-code-bot

docs/dyn/accesscontextmanager_v1.accessPolicies.servicePerimeters.html

@@ -163,6 +163,7 @@ <h3>Method Details</h3>
 
 { # `ServicePerimeter` describes a set of Google Cloud resources which can freely import and export data amongst themselves, but not export outside of the `ServicePerimeter`. If a request with a source within this `ServicePerimeter` has a target outside of the `ServicePerimeter`, the request will be blocked. Otherwise the request is allowed. There are two types of Service Perimeter - Regular and Bridge. Regular Service Perimeters cannot overlap, a single Google Cloud project or VPC network can only belong to a single regular Service Perimeter. Service Perimeter Bridges can contain only Google Cloud projects as members, a single Google Cloud project may belong to multiple Service Perimeter Bridges.
   &quot;description&quot;: &quot;A String&quot;, # Description of the `ServicePerimeter` and its use. Does not affect behavior.
+  &quot;etag&quot;: &quot;A String&quot;, # Optional. An opaque identifier for the current version of the `ServicePerimeter`. Clients should not expect this to be in any specific format. If etag is not provided, the operation will be performed as if a valid etag is provided.
   &quot;name&quot;: &quot;A String&quot;, # Identifier. Resource name for the `ServicePerimeter`. Format: `accessPolicies/{access_policy}/servicePerimeters/{service_perimeter}`. The `service_perimeter` component must begin with a letter, followed by alphanumeric characters or `_`. After you create a `ServicePerimeter`, you cannot change its `name`.
   &quot;perimeterType&quot;: &quot;A String&quot;, # Perimeter type indicator. A single project or VPC network is allowed to be a member of single regular perimeter, but multiple service perimeter bridges. A project cannot be a included in a perimeter bridge without being included in regular perimeter. For perimeter bridges, the restricted service list as well as access level lists must be empty.
   &quot;spec&quot;: { # `ServicePerimeterConfig` specifies a set of Google Cloud resources that describe specific Service Perimeter configuration. # Proposed (or dry run) ServicePerimeter configuration. This configuration allows to specify and test ServicePerimeter configuration without enforcing actual access restrictions. Only allowed to be set when the &quot;use_explicit_dry_run_spec&quot; flag is set.
@@ -417,6 +418,7 @@ <h3>Method Details</h3>
 
     { # `ServicePerimeter` describes a set of Google Cloud resources which can freely import and export data amongst themselves, but not export outside of the `ServicePerimeter`. If a request with a source within this `ServicePerimeter` has a target outside of the `ServicePerimeter`, the request will be blocked. Otherwise the request is allowed. There are two types of Service Perimeter - Regular and Bridge. Regular Service Perimeters cannot overlap, a single Google Cloud project or VPC network can only belong to a single regular Service Perimeter. Service Perimeter Bridges can contain only Google Cloud projects as members, a single Google Cloud project may belong to multiple Service Perimeter Bridges.
   &quot;description&quot;: &quot;A String&quot;, # Description of the `ServicePerimeter` and its use. Does not affect behavior.
+  &quot;etag&quot;: &quot;A String&quot;, # Optional. An opaque identifier for the current version of the `ServicePerimeter`. Clients should not expect this to be in any specific format. If etag is not provided, the operation will be performed as if a valid etag is provided.
   &quot;name&quot;: &quot;A String&quot;, # Identifier. Resource name for the `ServicePerimeter`. Format: `accessPolicies/{access_policy}/servicePerimeters/{service_perimeter}`. The `service_perimeter` component must begin with a letter, followed by alphanumeric characters or `_`. After you create a `ServicePerimeter`, you cannot change its `name`.
   &quot;perimeterType&quot;: &quot;A String&quot;, # Perimeter type indicator. A single project or VPC network is allowed to be a member of single regular perimeter, but multiple service perimeter bridges. A project cannot be a included in a perimeter bridge without being included in regular perimeter. For perimeter bridges, the restricted service list as well as access level lists must be empty.
   &quot;spec&quot;: { # `ServicePerimeterConfig` specifies a set of Google Cloud resources that describe specific Service Perimeter configuration. # Proposed (or dry run) ServicePerimeter configuration. This configuration allows to specify and test ServicePerimeter configuration without enforcing actual access restrictions. Only allowed to be set when the &quot;use_explicit_dry_run_spec&quot; flag is set.
@@ -613,6 +615,7 @@ <h3>Method Details</h3>
   &quot;servicePerimeters&quot;: [ # List of the Service Perimeter instances.
     { # `ServicePerimeter` describes a set of Google Cloud resources which can freely import and export data amongst themselves, but not export outside of the `ServicePerimeter`. If a request with a source within this `ServicePerimeter` has a target outside of the `ServicePerimeter`, the request will be blocked. Otherwise the request is allowed. There are two types of Service Perimeter - Regular and Bridge. Regular Service Perimeters cannot overlap, a single Google Cloud project or VPC network can only belong to a single regular Service Perimeter. Service Perimeter Bridges can contain only Google Cloud projects as members, a single Google Cloud project may belong to multiple Service Perimeter Bridges.
       &quot;description&quot;: &quot;A String&quot;, # Description of the `ServicePerimeter` and its use. Does not affect behavior.
+      &quot;etag&quot;: &quot;A String&quot;, # Optional. An opaque identifier for the current version of the `ServicePerimeter`. Clients should not expect this to be in any specific format. If etag is not provided, the operation will be performed as if a valid etag is provided.
       &quot;name&quot;: &quot;A String&quot;, # Identifier. Resource name for the `ServicePerimeter`. Format: `accessPolicies/{access_policy}/servicePerimeters/{service_perimeter}`. The `service_perimeter` component must begin with a letter, followed by alphanumeric characters or `_`. After you create a `ServicePerimeter`, you cannot change its `name`.
       &quot;perimeterType&quot;: &quot;A String&quot;, # Perimeter type indicator. A single project or VPC network is allowed to be a member of single regular perimeter, but multiple service perimeter bridges. A project cannot be a included in a perimeter bridge without being included in regular perimeter. For perimeter bridges, the restricted service list as well as access level lists must be empty.
       &quot;spec&quot;: { # `ServicePerimeterConfig` specifies a set of Google Cloud resources that describe specific Service Perimeter configuration. # Proposed (or dry run) ServicePerimeter configuration. This configuration allows to specify and test ServicePerimeter configuration without enforcing actual access restrictions. Only allowed to be set when the &quot;use_explicit_dry_run_spec&quot; flag is set.
@@ -815,6 +818,7 @@ <h3>Method Details</h3>
 
 { # `ServicePerimeter` describes a set of Google Cloud resources which can freely import and export data amongst themselves, but not export outside of the `ServicePerimeter`. If a request with a source within this `ServicePerimeter` has a target outside of the `ServicePerimeter`, the request will be blocked. Otherwise the request is allowed. There are two types of Service Perimeter - Regular and Bridge. Regular Service Perimeters cannot overlap, a single Google Cloud project or VPC network can only belong to a single regular Service Perimeter. Service Perimeter Bridges can contain only Google Cloud projects as members, a single Google Cloud project may belong to multiple Service Perimeter Bridges.
   &quot;description&quot;: &quot;A String&quot;, # Description of the `ServicePerimeter` and its use. Does not affect behavior.
+  &quot;etag&quot;: &quot;A String&quot;, # Optional. An opaque identifier for the current version of the `ServicePerimeter`. Clients should not expect this to be in any specific format. If etag is not provided, the operation will be performed as if a valid etag is provided.
   &quot;name&quot;: &quot;A String&quot;, # Identifier. Resource name for the `ServicePerimeter`. Format: `accessPolicies/{access_policy}/servicePerimeters/{service_perimeter}`. The `service_perimeter` component must begin with a letter, followed by alphanumeric characters or `_`. After you create a `ServicePerimeter`, you cannot change its `name`.
   &quot;perimeterType&quot;: &quot;A String&quot;, # Perimeter type indicator. A single project or VPC network is allowed to be a member of single regular perimeter, but multiple service perimeter bridges. A project cannot be a included in a perimeter bridge without being included in regular perimeter. For perimeter bridges, the restricted service list as well as access level lists must be empty.
   &quot;spec&quot;: { # `ServicePerimeterConfig` specifies a set of Google Cloud resources that describe specific Service Perimeter configuration. # Proposed (or dry run) ServicePerimeter configuration. This configuration allows to specify and test ServicePerimeter configuration without enforcing actual access restrictions. Only allowed to be set when the &quot;use_explicit_dry_run_spec&quot; flag is set.
@@ -1033,6 +1037,7 @@ <h3>Method Details</h3>
   &quot;servicePerimeters&quot;: [ # Required. The desired Service Perimeters that should replace all existing Service Perimeters in the Access Policy.
     { # `ServicePerimeter` describes a set of Google Cloud resources which can freely import and export data amongst themselves, but not export outside of the `ServicePerimeter`. If a request with a source within this `ServicePerimeter` has a target outside of the `ServicePerimeter`, the request will be blocked. Otherwise the request is allowed. There are two types of Service Perimeter - Regular and Bridge. Regular Service Perimeters cannot overlap, a single Google Cloud project or VPC network can only belong to a single regular Service Perimeter. Service Perimeter Bridges can contain only Google Cloud projects as members, a single Google Cloud project may belong to multiple Service Perimeter Bridges.
       &quot;description&quot;: &quot;A String&quot;, # Description of the `ServicePerimeter` and its use. Does not affect behavior.
+      &quot;etag&quot;: &quot;A String&quot;, # Optional. An opaque identifier for the current version of the `ServicePerimeter`. Clients should not expect this to be in any specific format. If etag is not provided, the operation will be performed as if a valid etag is provided.
       &quot;name&quot;: &quot;A String&quot;, # Identifier. Resource name for the `ServicePerimeter`. Format: `accessPolicies/{access_policy}/servicePerimeters/{service_perimeter}`. The `service_perimeter` component must begin with a letter, followed by alphanumeric characters or `_`. After you create a `ServicePerimeter`, you cannot change its `name`.
       &quot;perimeterType&quot;: &quot;A String&quot;, # Perimeter type indicator. A single project or VPC network is allowed to be a member of single regular perimeter, but multiple service perimeter bridges. A project cannot be a included in a perimeter bridge without being included in regular perimeter. For perimeter bridges, the restricted service list as well as access level lists must be empty.
       &quot;spec&quot;: { # `ServicePerimeterConfig` specifies a set of Google Cloud resources that describe specific Service Perimeter configuration. # Proposed (or dry run) ServicePerimeter configuration. This configuration allows to specify and test ServicePerimeter configuration without enforcing actual access restrictions. Only allowed to be set when the &quot;use_explicit_dry_run_spec&quot; flag is set.