Update ci_app description with max 1 year event run duration restriction (#898)

Co-authored-by: ci.datadog-api-spec <packages@datadoghq.com>

Author: api-clients-generation-pipeline[bot]

.generator/schemas/v2/openapi.yaml

@@ -57293,7 +57293,9 @@ paths:
 
 
         Pipeline events can be submitted with a timestamp that is up to 18 hours in
-        the past.'
+        the past.
+
+        The duration between the event start and end times cannot exceed 1 year.'
       operationId: CreateCIAppPipelineEvent
       requestBody:
         content:

src/datadogV2/api/api_ci_visibility_pipelines.rs

@@ -337,6 +337,7 @@ impl CIVisibilityPipelinesAPI {
     /// Multiple events can be sent in an array (up to 1000).
     ///
     /// Pipeline events can be submitted with a timestamp that is up to 18 hours in the past.
+    /// The duration between the event start and end times cannot exceed 1 year.
     pub async fn create_ci_app_pipeline_event(
         &self,
         body: crate::datadogV2::model::CIAppCreatePipelineEventRequest,
@@ -363,6 +364,7 @@ impl CIVisibilityPipelinesAPI {
     /// Multiple events can be sent in an array (up to 1000).
     ///
     /// Pipeline events can be submitted with a timestamp that is up to 18 hours in the past.
+    /// The duration between the event start and end times cannot exceed 1 year.
     pub async fn create_ci_app_pipeline_event_with_http_info(
         &self,
         body: crate::datadogV2::model::CIAppCreatePipelineEventRequest,