feat(networkmanagement): update the api

#### networkmanagement:v1

The following keys were added:
- schemas.Trace.properties.forwardTraceId (Total Keys: 2)

#### networkmanagement:v1beta1

The following keys were added:
- schemas.Trace.properties.forwardTraceId (Total Keys: 2)

Author: yoshi-automation

docs/dyn/networkmanagement_v1.projects.locations.global_.connectivityTests.html

@@ -214,6 +214,7 @@ <h3>Method Details</h3>
           &quot;sourceNetworkUri&quot;: &quot;A String&quot;, # URI of the network where this packet originates from.
           &quot;sourcePort&quot;: 42, # Source port. Only valid when protocol is TCP or UDP.
         },
+        &quot;forwardTraceId&quot;: 42, # ID of trace. For forward traces, this ID is unique for each trace. For return traces, it matches ID of associated forward trace. A single forward trace can be associated with none, one or more than one return trace.
         &quot;steps&quot;: [ # A trace of a test contains multiple steps from the initial state to the final state (delivered, dropped, forwarded, or aborted). The steps are ordered by the processing sequence within the simulated network state machine. It is critical to preserve the order of the steps and avoid reordering or sorting them.
           { # A simulated forwarding path is composed of multiple steps. Each step has a well-defined state and an associated configuration.
             &quot;abort&quot;: { # Details of the final state &quot;abort&quot; and associated resource. # Display information of the final state &quot;abort&quot; and reason.
@@ -648,6 +649,7 @@ <h3>Method Details</h3>
           &quot;sourceNetworkUri&quot;: &quot;A String&quot;, # URI of the network where this packet originates from.
           &quot;sourcePort&quot;: 42, # Source port. Only valid when protocol is TCP or UDP.
         },
+        &quot;forwardTraceId&quot;: 42, # ID of trace. For forward traces, this ID is unique for each trace. For return traces, it matches ID of associated forward trace. A single forward trace can be associated with none, one or more than one return trace.
         &quot;steps&quot;: [ # A trace of a test contains multiple steps from the initial state to the final state (delivered, dropped, forwarded, or aborted). The steps are ordered by the processing sequence within the simulated network state machine. It is critical to preserve the order of the steps and avoid reordering or sorting them.
           { # A simulated forwarding path is composed of multiple steps. Each step has a well-defined state and an associated configuration.
             &quot;abort&quot;: { # Details of the final state &quot;abort&quot; and associated resource. # Display information of the final state &quot;abort&quot; and reason.
@@ -1073,6 +1075,7 @@ <h3>Method Details</h3>
               &quot;sourceNetworkUri&quot;: &quot;A String&quot;, # URI of the network where this packet originates from.
               &quot;sourcePort&quot;: 42, # Source port. Only valid when protocol is TCP or UDP.
             },
+            &quot;forwardTraceId&quot;: 42, # ID of trace. For forward traces, this ID is unique for each trace. For return traces, it matches ID of associated forward trace. A single forward trace can be associated with none, one or more than one return trace.
             &quot;steps&quot;: [ # A trace of a test contains multiple steps from the initial state to the final state (delivered, dropped, forwarded, or aborted). The steps are ordered by the processing sequence within the simulated network state machine. It is critical to preserve the order of the steps and avoid reordering or sorting them.
               { # A simulated forwarding path is composed of multiple steps. Each step has a well-defined state and an associated configuration.
                 &quot;abort&quot;: { # Details of the final state &quot;abort&quot; and associated resource. # Display information of the final state &quot;abort&quot; and reason.
@@ -1457,6 +1460,7 @@ <h3>Method Details</h3>
           &quot;sourceNetworkUri&quot;: &quot;A String&quot;, # URI of the network where this packet originates from.
           &quot;sourcePort&quot;: 42, # Source port. Only valid when protocol is TCP or UDP.
         },
+        &quot;forwardTraceId&quot;: 42, # ID of trace. For forward traces, this ID is unique for each trace. For return traces, it matches ID of associated forward trace. A single forward trace can be associated with none, one or more than one return trace.
         &quot;steps&quot;: [ # A trace of a test contains multiple steps from the initial state to the final state (delivered, dropped, forwarded, or aborted). The steps are ordered by the processing sequence within the simulated network state machine. It is critical to preserve the order of the steps and avoid reordering or sorting them.
           { # A simulated forwarding path is composed of multiple steps. Each step has a well-defined state and an associated configuration.
             &quot;abort&quot;: { # Details of the final state &quot;abort&quot; and associated resource. # Display information of the final state &quot;abort&quot; and reason.

docs/dyn/networkmanagement_v1beta1.projects.locations.global_.connectivityTests.html

@@ -214,6 +214,7 @@ <h3>Method Details</h3>
           &quot;sourceNetworkUri&quot;: &quot;A String&quot;, # URI of the network where this packet originates from.
           &quot;sourcePort&quot;: 42, # Source port. Only valid when protocol is TCP or UDP.
         },
+        &quot;forwardTraceId&quot;: 42, # ID of trace. For forward traces, this ID is unique for each trace. For return traces, it matches ID of associated forward trace. A single forward trace can be associated with none, one or more than one return trace.
         &quot;steps&quot;: [ # A trace of a test contains multiple steps from the initial state to the final state (delivered, dropped, forwarded, or aborted). The steps are ordered by the processing sequence within the simulated network state machine. It is critical to preserve the order of the steps and avoid reordering or sorting them.
           { # A simulated forwarding path is composed of multiple steps. Each step has a well-defined state and an associated configuration.
             &quot;abort&quot;: { # Details of the final state &quot;abort&quot; and associated resource. # Display information of the final state &quot;abort&quot; and reason.
@@ -649,6 +650,7 @@ <h3>Method Details</h3>
           &quot;sourceNetworkUri&quot;: &quot;A String&quot;, # URI of the network where this packet originates from.
           &quot;sourcePort&quot;: 42, # Source port. Only valid when protocol is TCP or UDP.
         },
+        &quot;forwardTraceId&quot;: 42, # ID of trace. For forward traces, this ID is unique for each trace. For return traces, it matches ID of associated forward trace. A single forward trace can be associated with none, one or more than one return trace.
         &quot;steps&quot;: [ # A trace of a test contains multiple steps from the initial state to the final state (delivered, dropped, forwarded, or aborted). The steps are ordered by the processing sequence within the simulated network state machine. It is critical to preserve the order of the steps and avoid reordering or sorting them.
           { # A simulated forwarding path is composed of multiple steps. Each step has a well-defined state and an associated configuration.
             &quot;abort&quot;: { # Details of the final state &quot;abort&quot; and associated resource. # Display information of the final state &quot;abort&quot; and reason.
@@ -1075,6 +1077,7 @@ <h3>Method Details</h3>
               &quot;sourceNetworkUri&quot;: &quot;A String&quot;, # URI of the network where this packet originates from.
               &quot;sourcePort&quot;: 42, # Source port. Only valid when protocol is TCP or UDP.
             },
+            &quot;forwardTraceId&quot;: 42, # ID of trace. For forward traces, this ID is unique for each trace. For return traces, it matches ID of associated forward trace. A single forward trace can be associated with none, one or more than one return trace.
             &quot;steps&quot;: [ # A trace of a test contains multiple steps from the initial state to the final state (delivered, dropped, forwarded, or aborted). The steps are ordered by the processing sequence within the simulated network state machine. It is critical to preserve the order of the steps and avoid reordering or sorting them.
               { # A simulated forwarding path is composed of multiple steps. Each step has a well-defined state and an associated configuration.
                 &quot;abort&quot;: { # Details of the final state &quot;abort&quot; and associated resource. # Display information of the final state &quot;abort&quot; and reason.
@@ -1460,6 +1463,7 @@ <h3>Method Details</h3>
           &quot;sourceNetworkUri&quot;: &quot;A String&quot;, # URI of the network where this packet originates from.
           &quot;sourcePort&quot;: 42, # Source port. Only valid when protocol is TCP or UDP.
         },
+        &quot;forwardTraceId&quot;: 42, # ID of trace. For forward traces, this ID is unique for each trace. For return traces, it matches ID of associated forward trace. A single forward trace can be associated with none, one or more than one return trace.
         &quot;steps&quot;: [ # A trace of a test contains multiple steps from the initial state to the final state (delivered, dropped, forwarded, or aborted). The steps are ordered by the processing sequence within the simulated network state machine. It is critical to preserve the order of the steps and avoid reordering or sorting them.
           { # A simulated forwarding path is composed of multiple steps. Each step has a well-defined state and an associated configuration.
             &quot;abort&quot;: { # Details of the final state &quot;abort&quot; and associated resource. # Display information of the final state &quot;abort&quot; and reason.

googleapiclient/discovery_cache/documents/networkmanagement.v1.json

@@ -591,7 +591,7 @@
 }
 }
 },
-"revision": "20240124",
+"revision": "20240131",
 "rootUrl": "https://networkmanagement.googleapis.com/",
 "schemas": {
 "AbortInfo": {
@@ -2232,7 +2232,7 @@ false
 "No result was specified.",
 "Possible scenarios are: * The configuration analysis determined that a packet originating from the source is expected to reach the destination. * The analysis didn't complete because the user lacks permission for some of the resources in the trace. However, at the time the user's permission became insufficient, the trace had been successful so far.",
 "A packet originating from the source is expected to be dropped before reaching the destination.",
-"The source and destination endpoints do not uniquely identify the test location in the network, and the reachability result contains multiple traces. For some traces, a packet could be delivered, and for others, it would not be.",
+"The source and destination endpoints do not uniquely identify the test location in the network, and the reachability result contains multiple traces. For some traces, a packet could be delivered, and for others, it would not be. This result is also assigned to configuration analysis of return path if on its own it should be REACHABLE, but configuration analysis of forward path is AMBIGUOUS.",
 "The configuration analysis did not complete. Possible reasons are: * A permissions error occurred--for example, the user might not have read permission for all of the resources named in the test. * An internal error occurred. * The analyzer received an invalid or unsupported argument or was unable to identify a known endpoint."
 ],
 "type": "string"
@@ -2711,6 +2711,11 @@ false
 "$ref": "EndpointInfo",
 "description": "Derived from the source and destination endpoints definition specified by user request, and validated by the data plane model. If there are multiple traces starting from different source locations, then the endpoint_info may be different between traces."
 },
+"forwardTraceId": {
+"description": "ID of trace. For forward traces, this ID is unique for each trace. For return traces, it matches ID of associated forward trace. A single forward trace can be associated with none, one or more than one return trace.",
+"format": "int32",
+"type": "integer"
+},
 "steps": {
 "description": "A trace of a test contains multiple steps from the initial state to the final state (delivered, dropped, forwarded, or aborted). The steps are ordered by the processing sequence within the simulated network state machine. It is critical to preserve the order of the steps and avoid reordering or sorting them.",
 "items": {

googleapiclient/discovery_cache/documents/networkmanagement.v1beta1.json

@@ -591,7 +591,7 @@
 }
 }
 },
-"revision": "20240124",
+"revision": "20240131",
 "rootUrl": "https://networkmanagement.googleapis.com/",
 "schemas": {
 "AbortInfo": {
@@ -2237,7 +2237,7 @@ false
 "No result was specified.",
 "Possible scenarios are: * The configuration analysis determined that a packet originating from the source is expected to reach the destination. * The analysis didn't complete because the user lacks permission for some of the resources in the trace. However, at the time the user's permission became insufficient, the trace had been successful so far.",
 "A packet originating from the source is expected to be dropped before reaching the destination.",
-"The source and destination endpoints do not uniquely identify the test location in the network, and the reachability result contains multiple traces. For some traces, a packet could be delivered, and for others, it would not be.",
+"The source and destination endpoints do not uniquely identify the test location in the network, and the reachability result contains multiple traces. For some traces, a packet could be delivered, and for others, it would not be. This result is also assigned to configuration analysis of return path if on its own it should be REACHABLE, but configuration analysis of forward path is AMBIGUOUS.",
 "The configuration analysis did not complete. Possible reasons are: * A permissions error occurred--for example, the user might not have read permission for all of the resources named in the test. * An internal error occurred. * The analyzer received an invalid or unsupported argument or was unable to identify a known endpoint."
 ],
 "type": "string"
@@ -2716,6 +2716,11 @@ false
 "$ref": "EndpointInfo",
 "description": "Derived from the source and destination endpoints definition specified by user request, and validated by the data plane model. If there are multiple traces starting from different source locations, then the endpoint_info may be different between traces."
 },
+"forwardTraceId": {
+"description": "ID of trace. For forward traces, this ID is unique for each trace. For return traces, it matches ID of associated forward trace. A single forward trace can be associated with none, one or more than one return trace.",
+"format": "int32",
+"type": "integer"
+},
 "steps": {
 "description": "A trace of a test contains multiple steps from the initial state to the final state (delivered, dropped, forwarded, or aborted). The steps are ordered by the processing sequence within the simulated network state machine. It is critical to preserve the order of the steps and avoid reordering or sorting them.",
 "items": {