Skip invalid test for rust (#1552)

Co-authored-by: ci.datadog-api-spec <[email protected]>

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

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-03-08 14:49:41.084247",
-            "spec_repo_commit": "f5ed7e52"
+            "regenerated": "2024-03-11 14:09:24.763861",
+            "spec_repo_commit": "0f7ad8f2"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-03-08 14:49:41.101800",
-            "spec_repo_commit": "f5ed7e52"
+            "regenerated": "2024-03-11 14:09:24.781621",
+            "spec_repo_commit": "0f7ad8f2"
         }
     }
 }

features/v2/downtimes.feature

@@ -111,7 +111,7 @@ Feature: Downtimes
     Then the response status is 200 OK
     And the response "data.attributes.message" is equal to "dark forest"
 
-  @skip-java @skip-python @skip-ruby @skip-typescript @skip-validation @team:DataDog/monitor-app
+  @skip-java @skip-python @skip-ruby @skip-rust @skip-typescript @skip-validation @team:DataDog/monitor-app
   Scenario: Update a downtime returns "Bad Request" response
     Given there is a valid "downtime_v2" in the system
     And new "UpdateDowntime" request