Skip gcp STS validation tests for now (#1327)

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

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

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.5",
-            "regenerated": "2023-09-15 14:38:35.203433",
-            "spec_repo_commit": "dfa5ada6"
+            "regenerated": "2023-09-18 19:41:20.469205",
+            "spec_repo_commit": "0e1d17c9"
         },
         "v2": {
             "apigentools_version": "1.6.5",
-            "regenerated": "2023-09-15 14:38:35.289343",
-            "spec_repo_commit": "dfa5ada6"
+            "regenerated": "2023-09-18 19:41:20.485433",
+            "spec_repo_commit": "0e1d17c9"
         }
     }
 }

features/v2/gcp_integration.feature

@@ -45,7 +45,7 @@ Feature: GCP Integration
     When the request is sent
     Then the response status is 409 Conflict
 
-  @team:DataDog/gcp-integrations
+  @skip-validation @team:DataDog/gcp-integrations
   Scenario: Create a new entry for your service account returns "OK" response
     Given new "CreateGCPSTSAccount" request
     And body with value {"data": {"attributes": {"client_email": "{{ unique_hash }}@test-project.iam.gserviceaccount.com", "host_filters": []}, "type": "gcp_service_account"}}
@@ -74,7 +74,7 @@ Feature: GCP Integration
     When the request is sent
     Then the response status is 404 Not Found
 
-  @team:DataDog/gcp-integrations
+  @skip-validation @team:DataDog/gcp-integrations
   Scenario: List all GCP STS-enabled service accounts returns "OK" response
     Given there is a valid "gcp_sts_account" in the system
     And new "ListGCPSTSAccounts" request
@@ -105,7 +105,7 @@ Feature: GCP Integration
     When the request is sent
     Then the response status is 404 Not Found
 
-  @team:DataDog/gcp-integrations
+  @skip-validation @team:DataDog/gcp-integrations
   Scenario: Update STS Service Account returns "OK" response
     Given there is a valid "gcp_sts_account" in the system
     And new "UpdateGCPSTSAccount" request