Regenerate client from commit 4f16ecfe of spec repo

Author: ci.datadog-api-spec

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-04-16 20:32:57.249173",
-            "spec_repo_commit": "9708d631"
+            "regenerated": "2025-04-17 05:43:33.149342",
+            "spec_repo_commit": "4f16ecfe"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-04-16 20:32:57.267116",
-            "spec_repo_commit": "9708d631"
+            "regenerated": "2025-04-17 05:43:33.165411",
+            "spec_repo_commit": "4f16ecfe"
         }
     }
 }

src/test/resources/com/datadog/api/client/v2/api/on-call.feature

@@ -33,7 +33,7 @@ Feature: On-Call
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @skip-python @team:DataDog/bugle
+  @team:DataDog/bugle
   Scenario: Create on-call schedule returns "Created" response
     Given new "CreateOnCallSchedule" request
     And there is a valid "user" in the system
@@ -159,7 +159,7 @@ Feature: On-Call
     When the request is sent
     Then the response status is 404 Not Found
 
-  @skip-python @team:DataDog/bugle
+  @team:DataDog/bugle
   Scenario: Update on-call schedule returns "OK" response
     Given new "UpdateOnCallSchedule" request
     And there is a valid "schedule" in the system