Regenerate client from commit f7db18b of spec repo (#534)

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.4.1.dev11",
-            "regenerated": "2021-08-09 09:22:24.096659",
-            "spec_repo_commit": "7c3089e"
+            "regenerated": "2021-08-09 14:31:45.996631",
+            "spec_repo_commit": "f7db18b"
         },
         "v2": {
             "apigentools_version": "1.4.1.dev11",
-            "regenerated": "2021-08-09 09:22:50.599634",
-            "spec_repo_commit": "7c3089e"
+            "regenerated": "2021-08-09 14:32:10.644831",
+            "spec_repo_commit": "f7db18b"
         }
     }
 }

docs/v1/SLOHistorySLIData.md

@@ -15,7 +15,7 @@ Feature: Synthetics
     And a valid "appKeyAuth" key in the system
     And an instance of "Synthetics" API
 
-  @replay-only @skip-python @skip-java @skip-ruby
+  @replay-only @skip-java @skip-python @skip-ruby
   Scenario: Client is resilient to enum and oneOf deserialization errors
     Given new "ListTests" request
     When the request is sent