Enable Rust sdk generation pipeline (#2233)

Co-authored-by: ci.datadog-api-spec <[email protected]>
Co-authored-by: api-clients-generation-pipeline[bot] <54105614+api-clients-generation-pipeline[bot]@users.noreply.github.com>

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-03-21 18:00:31.538811",
-            "spec_repo_commit": "65baee0e"
+            "regenerated": "2024-03-21 19:44:30.594881",
+            "spec_repo_commit": "7b0d4cbe"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-03-21 18:00:31.554784",
-            "spec_repo_commit": "65baee0e"
+            "regenerated": "2024-03-21 19:44:30.612203",
+            "spec_repo_commit": "7b0d4cbe"
         }
     }
 }

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

@@ -75,7 +75,7 @@ Feature: Logs Custom Destinations
     And the response "data.attributes.forward_tags_restriction_list" array contains value "host"
     And the response "data.attributes.forward_tags_restriction_list_type" is equal to "ALLOW_LIST"
 
-  @skip-java @skip-python @skip-typescript @team:DataDog/logs-backend
+  @skip-java @skip-python @skip-rust @skip-typescript @team:DataDog/logs-backend
   Scenario: Create a custom destination returns "Bad Request" response
     Given new "CreateLogsCustomDestination" request
     And body with value {"data": {"attributes": {"name": "Nginx logs"}, "type": "custom_destination"}}

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

@@ -9,7 +9,7 @@ Feature: Organizations
     And an instance of "Organizations" API
     And new "UploadIdPMetadata" request
 
-  @skip-go @skip-java @skip-python @skip-ruby @skip-terraform-config @skip-typescript @skip-validation @team:DataDog/team-aaa-identity
+  @skip-go @skip-java @skip-python @skip-ruby @skip-rust @skip-terraform-config @skip-typescript @skip-validation @team:DataDog/team-aaa-identity
   Scenario: Upload IdP metadata returns "Bad Request - caused by either malformed XML or invalid SAML IdP metadata" response
     Given request contains "idp_file" parameter with value "fixtures/organizations/saml_configurations/invalid_idp_metadata.xml"
     When the request is sent