Regenerate client from commit 3c19b3ae of spec repo

Author: ci.datadog-api-spec

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-12-13 16:09:25.530948",
-            "spec_repo_commit": "936a5463"
+            "regenerated": "2024-12-13 22:22:52.092685",
+            "spec_repo_commit": "3c19b3ae"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-12-13 16:09:25.549581",
-            "spec_repo_commit": "936a5463"
+            "regenerated": "2024-12-13 22:22:52.114784",
+            "spec_repo_commit": "3c19b3ae"
         }
     }
 }

src/test/resources/com/datadog/api/client/v2/api/ci_visibility_pipelines.feature

@@ -108,7 +108,7 @@ Feature: CI Visibility Pipelines
     When the request is sent
     Then the response status is 202 Request accepted for processing
 
-  @skip @team:Datadog/ci-app-backend
+  @skip-typescript @team:Datadog/ci-app-backend
   Scenario: Send pipeline job event returns "Request accepted for processing" response
     Given new "CreateCIAppPipelineEvent" request
     And body with value {"data": {"attributes": {"resource": {"level": "job", "id": "cf9456de-8b9e-4c27-aa79-27b1e78c1a33", "name": "Build image", "pipeline_unique_id": "3eacb6f3-ff04-4e10-8a9c-46e6d054024a", "pipeline_name": "Deploy to AWS", "start": "{{ timeISO('now - 120s') }}", "end": "{{ timeISO('now - 30s') }}", "status": "error", "url": "https://my-ci-provider.example/jobs/my-jobs/run/1"}}, "type": "cipipeline_resource_request"}}