Regenerate client from commit d8a79527 of spec repo (#1545)

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.2",
-            "regenerated": "2022-06-14 08:16:18.622596",
-            "spec_repo_commit": "0f6264a5"
+            "regenerated": "2022-06-14 13:57:35.613820",
+            "spec_repo_commit": "d8a79527"
         },
         "v2": {
             "apigentools_version": "1.6.2",
-            "regenerated": "2022-06-14 08:16:18.634865",
-            "spec_repo_commit": "0f6264a5"
+            "regenerated": "2022-06-14 13:57:35.629222",
+            "spec_repo_commit": "d8a79527"
         }
     }
 }

tests/scenarios/features/v1/aws_integration.feature

@@ -139,7 +139,7 @@ Feature: AWS Integration
     When the request is sent
     Then the response status is 409 Conflict Error
 
-  @replay-only @team:DataDog/cloud-integrations
+  @replay-only @skip-typescript @team:DataDog/cloud-integrations
   Scenario: Update an AWS integration returns "OK" response
     Given new "UpdateAWSAccount" request
     And body with value {"account_id": "123456789012", "account_specific_namespace_rules": {"auto_scaling": false}, "cspm_resource_collection_enabled": true, "excluded_regions": ["us-east-1", "us-west-2"], "filter_tags": ["$KEY:$VALUE"], "host_tags": ["$KEY:$VALUE"], "metrics_collection_enabled": false, "resource_collection_enabled": true, "role_name": "datadog-role"}