feat(networkconnectivity): update the api

#### networkconnectivity:v1

The following keys were added:
- schemas.LinkedVpcNetwork.properties.includeExportRanges (Total Keys: 2)

Author: yoshi-automation

docs/dyn/networkconnectivity_v1.projects.locations.global_.hubs.html

@@ -529,6 +529,9 @@ <h3>Method Details</h3>
         &quot;excludeExportRanges&quot;: [ # Optional. IP ranges encompassing the subnets to be excluded from peering.
           &quot;A String&quot;,
         ],
+        &quot;includeExportRanges&quot;: [ # Optional. IP ranges allowed to be included from peering.
+          &quot;A String&quot;,
+        ],
         &quot;uri&quot;: &quot;A String&quot;, # Required. The URI of the VPC network resource.
       },
       &quot;linkedVpnTunnels&quot;: { # A collection of Cloud VPN tunnel resources. These resources should be redundant HA VPN tunnels that all advertise the same prefixes to Google Cloud. Alternatively, in a passive/active configuration, all tunnels should be capable of advertising the same prefixes. # VPN tunnels that are associated with the spoke.

docs/dyn/networkconnectivity_v1.projects.locations.spokes.html

@@ -148,6 +148,9 @@ <h3>Method Details</h3>
     &quot;excludeExportRanges&quot;: [ # Optional. IP ranges encompassing the subnets to be excluded from peering.
       &quot;A String&quot;,
     ],
+    &quot;includeExportRanges&quot;: [ # Optional. IP ranges allowed to be included from peering.
+      &quot;A String&quot;,
+    ],
     &quot;uri&quot;: &quot;A String&quot;, # Required. The URI of the VPC network resource.
   },
   &quot;linkedVpnTunnels&quot;: { # A collection of Cloud VPN tunnel resources. These resources should be redundant HA VPN tunnels that all advertise the same prefixes to Google Cloud. Alternatively, in a passive/active configuration, all tunnels should be capable of advertising the same prefixes. # VPN tunnels that are associated with the spoke.
@@ -281,6 +284,9 @@ <h3>Method Details</h3>
     &quot;excludeExportRanges&quot;: [ # Optional. IP ranges encompassing the subnets to be excluded from peering.
       &quot;A String&quot;,
     ],
+    &quot;includeExportRanges&quot;: [ # Optional. IP ranges allowed to be included from peering.
+      &quot;A String&quot;,
+    ],
     &quot;uri&quot;: &quot;A String&quot;, # Required. The URI of the VPC network resource.
   },
   &quot;linkedVpnTunnels&quot;: { # A collection of Cloud VPN tunnel resources. These resources should be redundant HA VPN tunnels that all advertise the same prefixes to Google Cloud. Alternatively, in a passive/active configuration, all tunnels should be capable of advertising the same prefixes. # VPN tunnels that are associated with the spoke.
@@ -403,6 +409,9 @@ <h3>Method Details</h3>
         &quot;excludeExportRanges&quot;: [ # Optional. IP ranges encompassing the subnets to be excluded from peering.
           &quot;A String&quot;,
         ],
+        &quot;includeExportRanges&quot;: [ # Optional. IP ranges allowed to be included from peering.
+          &quot;A String&quot;,
+        ],
         &quot;uri&quot;: &quot;A String&quot;, # Required. The URI of the VPC network resource.
       },
       &quot;linkedVpnTunnels&quot;: { # A collection of Cloud VPN tunnel resources. These resources should be redundant HA VPN tunnels that all advertise the same prefixes to Google Cloud. Alternatively, in a passive/active configuration, all tunnels should be capable of advertising the same prefixes. # VPN tunnels that are associated with the spoke.
@@ -484,6 +493,9 @@ <h3>Method Details</h3>
     &quot;excludeExportRanges&quot;: [ # Optional. IP ranges encompassing the subnets to be excluded from peering.
       &quot;A String&quot;,
     ],
+    &quot;includeExportRanges&quot;: [ # Optional. IP ranges allowed to be included from peering.
+      &quot;A String&quot;,
+    ],
     &quot;uri&quot;: &quot;A String&quot;, # Required. The URI of the VPC network resource.
   },
   &quot;linkedVpnTunnels&quot;: { # A collection of Cloud VPN tunnel resources. These resources should be redundant HA VPN tunnels that all advertise the same prefixes to Google Cloud. Alternatively, in a passive/active configuration, all tunnels should be capable of advertising the same prefixes. # VPN tunnels that are associated with the spoke.

googleapiclient/discovery_cache/documents/networkconnectivity.v1.json

@@ -2812,7 +2812,7 @@
 }
 }
 },
-"revision": "20240523",
+"revision": "20240529",
 "rootUrl": "https://networkconnectivity.googleapis.com/",
 "schemas": {
 "AcceptHubSpokeRequest": {
@@ -3595,6 +3595,13 @@
 },
 "type": "array"
 },
+"includeExportRanges": {
+"description": "Optional. IP ranges allowed to be included from peering.",
+"items": {
+"type": "string"
+},
+"type": "array"
+},
 "uri": {
 "description": "Required. The URI of the VPC network resource.",
 "type": "string"

googleapiclient/discovery_cache/documents/networkconnectivity.v1alpha1.json

@@ -1116,7 +1116,7 @@
 }
 }
 },
-"revision": "20240523",
+"revision": "20240529",
 "rootUrl": "https://networkconnectivity.googleapis.com/",
 "schemas": {
 "AuditConfig": {