feat(dialogflow): update the api

#### dialogflow:v2

The following keys were added:
- schemas.GoogleCloudDialogflowV2ConversationEvent.properties.newRecognitionResultPayload.$ref (Total Keys: 1)
- schemas.GoogleCloudDialogflowV2ConversationProfile.properties.newRecognitionResultNotificationConfig.$ref (Total Keys: 1)
- schemas.GoogleCloudDialogflowV2SpeechWordInfo (Total Keys: 9)
- schemas.GoogleCloudDialogflowV2StreamingRecognitionResult (Total Keys: 12)
- schemas.GoogleCloudDialogflowV2beta1ConversationEvent.properties.newRecognitionResultPayload.$ref (Total Keys: 1)
- schemas.GoogleCloudDialogflowV2beta1SpeechWordInfo (Total Keys: 9)
- schemas.GoogleCloudDialogflowV2beta1StreamingRecognitionResult (Total Keys: 15)
- schemas.GoogleCloudDialogflowV2beta1TelephonyDtmfEvents (Total Keys: 4)

#### dialogflow:v2beta1

The following keys were added:
- schemas.GoogleCloudDialogflowV2ConversationEvent.properties.newRecognitionResultPayload.$ref (Total Keys: 1)
- schemas.GoogleCloudDialogflowV2SpeechWordInfo (Total Keys: 9)
- schemas.GoogleCloudDialogflowV2StreamingRecognitionResult (Total Keys: 12)
- schemas.GoogleCloudDialogflowV2beta1ConversationEvent.properties.newRecognitionResultPayload.$ref (Total Keys: 1)
- schemas.GoogleCloudDialogflowV2beta1ConversationProfile.properties.newRecognitionResultNotificationConfig.$ref (Total Keys: 1)
- schemas.GoogleCloudDialogflowV2beta1SpeechWordInfo (Total Keys: 9)
- schemas.GoogleCloudDialogflowV2beta1StreamingRecognitionResult (Total Keys: 15)

#### dialogflow:v3

The following keys were added:
- schemas.GoogleCloudDialogflowV2ConversationEvent.properties.newRecognitionResultPayload.$ref (Total Keys: 1)
- schemas.GoogleCloudDialogflowV2SpeechWordInfo (Total Keys: 9)
- schemas.GoogleCloudDialogflowV2StreamingRecognitionResult (Total Keys: 12)
- schemas.GoogleCloudDialogflowV2beta1ConversationEvent.properties.newRecognitionResultPayload.$ref (Total Keys: 1)
- schemas.GoogleCloudDialogflowV2beta1SpeechWordInfo (Total Keys: 9)
- schemas.GoogleCloudDialogflowV2beta1StreamingRecognitionResult (Total Keys: 15)
- schemas.GoogleCloudDialogflowV2beta1TelephonyDtmfEvents (Total Keys: 4)

#### dialogflow:v3beta1

The following keys were added:
- schemas.GoogleCloudDialogflowCxV3beta1ConversationInteraction.properties.stepMetrics (Total Keys: 2)
- schemas.GoogleCloudDialogflowCxV3beta1ConversationInteractionStepMetrics (Total Keys: 5)
- schemas.GoogleCloudDialogflowV2ConversationEvent.properties.newRecognitionResultPayload.$ref (Total Keys: 1)
- schemas.GoogleCloudDialogflowV2SpeechWordInfo (Total Keys: 9)
- schemas.GoogleCloudDialogflowV2StreamingRecognitionResult (Total Keys: 12)
- schemas.GoogleCloudDialogflowV2beta1ConversationEvent.properties.newRecognitionResultPayload.$ref (Total Keys: 1)
- schemas.GoogleCloudDialogflowV2beta1SpeechWordInfo (Total Keys: 9)
- schemas.GoogleCloudDialogflowV2beta1StreamingRecognitionResult (Total Keys: 15)
- schemas.GoogleCloudDialogflowV2beta1TelephonyDtmfEvents (Total Keys: 4)

Author: yoshi-automation

docs/dyn/dialogflow_v2.projects.conversationProfiles.html

@@ -318,6 +318,10 @@ <h3>Method Details</h3>
     &quot;messageFormat&quot;: &quot;A String&quot;, # Format of message.
     &quot;topic&quot;: &quot;A String&quot;, # Name of the Pub/Sub topic to publish conversation events like CONVERSATION_STARTED as serialized ConversationEvent protos. For telephony integration to receive notification, make sure either this topic is in the same project as the conversation or you grant `[email protected]` the `Dialogflow Service Agent` role in the topic project. For chat integration to receive notification, make sure API caller has been granted the `Dialogflow Service Agent` role for the topic. Format: `projects//locations//topics/`.
   },
+  &quot;newRecognitionResultNotificationConfig&quot;: { # Defines notification behavior. # Optional. Configuration for publishing transcription intermediate results. Event will be sent in format of ConversationEvent. If configured, the following information will be populated as ConversationEvent Pub/Sub message attributes: - &quot;participant_id&quot; - &quot;participant_role&quot; - &quot;message_id&quot;
+    &quot;messageFormat&quot;: &quot;A String&quot;, # Format of message.
+    &quot;topic&quot;: &quot;A String&quot;, # Name of the Pub/Sub topic to publish conversation events like CONVERSATION_STARTED as serialized ConversationEvent protos. For telephony integration to receive notification, make sure either this topic is in the same project as the conversation or you grant `[email protected]` the `Dialogflow Service Agent` role in the topic project. For chat integration to receive notification, make sure API caller has been granted the `Dialogflow Service Agent` role for the topic. Format: `projects//locations//topics/`.
+  },
   &quot;notificationConfig&quot;: { # Defines notification behavior. # Configuration for publishing conversation lifecycle events.
     &quot;messageFormat&quot;: &quot;A String&quot;, # Format of message.
     &quot;topic&quot;: &quot;A String&quot;, # Name of the Pub/Sub topic to publish conversation events like CONVERSATION_STARTED as serialized ConversationEvent protos. For telephony integration to receive notification, make sure either this topic is in the same project as the conversation or you grant `[email protected]` the `Dialogflow Service Agent` role in the topic project. For chat integration to receive notification, make sure API caller has been granted the `Dialogflow Service Agent` role for the topic. Format: `projects//locations//topics/`.
@@ -518,6 +522,10 @@ <h3>Method Details</h3>
     &quot;messageFormat&quot;: &quot;A String&quot;, # Format of message.
     &quot;topic&quot;: &quot;A String&quot;, # Name of the Pub/Sub topic to publish conversation events like CONVERSATION_STARTED as serialized ConversationEvent protos. For telephony integration to receive notification, make sure either this topic is in the same project as the conversation or you grant `[email protected]` the `Dialogflow Service Agent` role in the topic project. For chat integration to receive notification, make sure API caller has been granted the `Dialogflow Service Agent` role for the topic. Format: `projects//locations//topics/`.
   },
+  &quot;newRecognitionResultNotificationConfig&quot;: { # Defines notification behavior. # Optional. Configuration for publishing transcription intermediate results. Event will be sent in format of ConversationEvent. If configured, the following information will be populated as ConversationEvent Pub/Sub message attributes: - &quot;participant_id&quot; - &quot;participant_role&quot; - &quot;message_id&quot;
+    &quot;messageFormat&quot;: &quot;A String&quot;, # Format of message.
+    &quot;topic&quot;: &quot;A String&quot;, # Name of the Pub/Sub topic to publish conversation events like CONVERSATION_STARTED as serialized ConversationEvent protos. For telephony integration to receive notification, make sure either this topic is in the same project as the conversation or you grant `[email protected]` the `Dialogflow Service Agent` role in the topic project. For chat integration to receive notification, make sure API caller has been granted the `Dialogflow Service Agent` role for the topic. Format: `projects//locations//topics/`.
+  },
   &quot;notificationConfig&quot;: { # Defines notification behavior. # Configuration for publishing conversation lifecycle events.
     &quot;messageFormat&quot;: &quot;A String&quot;, # Format of message.
     &quot;topic&quot;: &quot;A String&quot;, # Name of the Pub/Sub topic to publish conversation events like CONVERSATION_STARTED as serialized ConversationEvent protos. For telephony integration to receive notification, make sure either this topic is in the same project as the conversation or you grant `[email protected]` the `Dialogflow Service Agent` role in the topic project. For chat integration to receive notification, make sure API caller has been granted the `Dialogflow Service Agent` role for the topic. Format: `projects//locations//topics/`.
@@ -743,6 +751,10 @@ <h3>Method Details</h3>
     &quot;messageFormat&quot;: &quot;A String&quot;, # Format of message.
     &quot;topic&quot;: &quot;A String&quot;, # Name of the Pub/Sub topic to publish conversation events like CONVERSATION_STARTED as serialized ConversationEvent protos. For telephony integration to receive notification, make sure either this topic is in the same project as the conversation or you grant `[email protected]` the `Dialogflow Service Agent` role in the topic project. For chat integration to receive notification, make sure API caller has been granted the `Dialogflow Service Agent` role for the topic. Format: `projects//locations//topics/`.
   },
+  &quot;newRecognitionResultNotificationConfig&quot;: { # Defines notification behavior. # Optional. Configuration for publishing transcription intermediate results. Event will be sent in format of ConversationEvent. If configured, the following information will be populated as ConversationEvent Pub/Sub message attributes: - &quot;participant_id&quot; - &quot;participant_role&quot; - &quot;message_id&quot;
+    &quot;messageFormat&quot;: &quot;A String&quot;, # Format of message.
+    &quot;topic&quot;: &quot;A String&quot;, # Name of the Pub/Sub topic to publish conversation events like CONVERSATION_STARTED as serialized ConversationEvent protos. For telephony integration to receive notification, make sure either this topic is in the same project as the conversation or you grant `[email protected]` the `Dialogflow Service Agent` role in the topic project. For chat integration to receive notification, make sure API caller has been granted the `Dialogflow Service Agent` role for the topic. Format: `projects//locations//topics/`.
+  },
   &quot;notificationConfig&quot;: { # Defines notification behavior. # Configuration for publishing conversation lifecycle events.
     &quot;messageFormat&quot;: &quot;A String&quot;, # Format of message.
     &quot;topic&quot;: &quot;A String&quot;, # Name of the Pub/Sub topic to publish conversation events like CONVERSATION_STARTED as serialized ConversationEvent protos. For telephony integration to receive notification, make sure either this topic is in the same project as the conversation or you grant `[email protected]` the `Dialogflow Service Agent` role in the topic project. For chat integration to receive notification, make sure API caller has been granted the `Dialogflow Service Agent` role for the topic. Format: `projects//locations//topics/`.
@@ -954,6 +966,10 @@ <h3>Method Details</h3>
         &quot;messageFormat&quot;: &quot;A String&quot;, # Format of message.
         &quot;topic&quot;: &quot;A String&quot;, # Name of the Pub/Sub topic to publish conversation events like CONVERSATION_STARTED as serialized ConversationEvent protos. For telephony integration to receive notification, make sure either this topic is in the same project as the conversation or you grant `[email protected]` the `Dialogflow Service Agent` role in the topic project. For chat integration to receive notification, make sure API caller has been granted the `Dialogflow Service Agent` role for the topic. Format: `projects//locations//topics/`.
       },
+      &quot;newRecognitionResultNotificationConfig&quot;: { # Defines notification behavior. # Optional. Configuration for publishing transcription intermediate results. Event will be sent in format of ConversationEvent. If configured, the following information will be populated as ConversationEvent Pub/Sub message attributes: - &quot;participant_id&quot; - &quot;participant_role&quot; - &quot;message_id&quot;
+        &quot;messageFormat&quot;: &quot;A String&quot;, # Format of message.
+        &quot;topic&quot;: &quot;A String&quot;, # Name of the Pub/Sub topic to publish conversation events like CONVERSATION_STARTED as serialized ConversationEvent protos. For telephony integration to receive notification, make sure either this topic is in the same project as the conversation or you grant `[email protected]` the `Dialogflow Service Agent` role in the topic project. For chat integration to receive notification, make sure API caller has been granted the `Dialogflow Service Agent` role for the topic. Format: `projects//locations//topics/`.
+      },
       &quot;notificationConfig&quot;: { # Defines notification behavior. # Configuration for publishing conversation lifecycle events.
         &quot;messageFormat&quot;: &quot;A String&quot;, # Format of message.
         &quot;topic&quot;: &quot;A String&quot;, # Name of the Pub/Sub topic to publish conversation events like CONVERSATION_STARTED as serialized ConversationEvent protos. For telephony integration to receive notification, make sure either this topic is in the same project as the conversation or you grant `[email protected]` the `Dialogflow Service Agent` role in the topic project. For chat integration to receive notification, make sure API caller has been granted the `Dialogflow Service Agent` role for the topic. Format: `projects//locations//topics/`.
@@ -1173,6 +1189,10 @@ <h3>Method Details</h3>
     &quot;messageFormat&quot;: &quot;A String&quot;, # Format of message.
     &quot;topic&quot;: &quot;A String&quot;, # Name of the Pub/Sub topic to publish conversation events like CONVERSATION_STARTED as serialized ConversationEvent protos. For telephony integration to receive notification, make sure either this topic is in the same project as the conversation or you grant `[email protected]` the `Dialogflow Service Agent` role in the topic project. For chat integration to receive notification, make sure API caller has been granted the `Dialogflow Service Agent` role for the topic. Format: `projects//locations//topics/`.
   },
+  &quot;newRecognitionResultNotificationConfig&quot;: { # Defines notification behavior. # Optional. Configuration for publishing transcription intermediate results. Event will be sent in format of ConversationEvent. If configured, the following information will be populated as ConversationEvent Pub/Sub message attributes: - &quot;participant_id&quot; - &quot;participant_role&quot; - &quot;message_id&quot;
+    &quot;messageFormat&quot;: &quot;A String&quot;, # Format of message.
+    &quot;topic&quot;: &quot;A String&quot;, # Name of the Pub/Sub topic to publish conversation events like CONVERSATION_STARTED as serialized ConversationEvent protos. For telephony integration to receive notification, make sure either this topic is in the same project as the conversation or you grant `[email protected]` the `Dialogflow Service Agent` role in the topic project. For chat integration to receive notification, make sure API caller has been granted the `Dialogflow Service Agent` role for the topic. Format: `projects//locations//topics/`.
+  },
   &quot;notificationConfig&quot;: { # Defines notification behavior. # Configuration for publishing conversation lifecycle events.
     &quot;messageFormat&quot;: &quot;A String&quot;, # Format of message.
     &quot;topic&quot;: &quot;A String&quot;, # Name of the Pub/Sub topic to publish conversation events like CONVERSATION_STARTED as serialized ConversationEvent protos. For telephony integration to receive notification, make sure either this topic is in the same project as the conversation or you grant `[email protected]` the `Dialogflow Service Agent` role in the topic project. For chat integration to receive notification, make sure API caller has been granted the `Dialogflow Service Agent` role for the topic. Format: `projects//locations//topics/`.
@@ -1374,6 +1394,10 @@ <h3>Method Details</h3>
     &quot;messageFormat&quot;: &quot;A String&quot;, # Format of message.
     &quot;topic&quot;: &quot;A String&quot;, # Name of the Pub/Sub topic to publish conversation events like CONVERSATION_STARTED as serialized ConversationEvent protos. For telephony integration to receive notification, make sure either this topic is in the same project as the conversation or you grant `[email protected]` the `Dialogflow Service Agent` role in the topic project. For chat integration to receive notification, make sure API caller has been granted the `Dialogflow Service Agent` role for the topic. Format: `projects//locations//topics/`.
   },
+  &quot;newRecognitionResultNotificationConfig&quot;: { # Defines notification behavior. # Optional. Configuration for publishing transcription intermediate results. Event will be sent in format of ConversationEvent. If configured, the following information will be populated as ConversationEvent Pub/Sub message attributes: - &quot;participant_id&quot; - &quot;participant_role&quot; - &quot;message_id&quot;
+    &quot;messageFormat&quot;: &quot;A String&quot;, # Format of message.
+    &quot;topic&quot;: &quot;A String&quot;, # Name of the Pub/Sub topic to publish conversation events like CONVERSATION_STARTED as serialized ConversationEvent protos. For telephony integration to receive notification, make sure either this topic is in the same project as the conversation or you grant `[email protected]` the `Dialogflow Service Agent` role in the topic project. For chat integration to receive notification, make sure API caller has been granted the `Dialogflow Service Agent` role for the topic. Format: `projects//locations//topics/`.
+  },
   &quot;notificationConfig&quot;: { # Defines notification behavior. # Configuration for publishing conversation lifecycle events.
     &quot;messageFormat&quot;: &quot;A String&quot;, # Format of message.
     &quot;topic&quot;: &quot;A String&quot;, # Name of the Pub/Sub topic to publish conversation events like CONVERSATION_STARTED as serialized ConversationEvent protos. For telephony integration to receive notification, make sure either this topic is in the same project as the conversation or you grant `[email protected]` the `Dialogflow Service Agent` role in the topic project. For chat integration to receive notification, make sure API caller has been granted the `Dialogflow Service Agent` role for the topic. Format: `projects//locations//topics/`.