Add Sev0 as a supported incident severity (#2403)

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.6.6",
-            "regenerated": "2025-05-07 21:19:51.630719",
-            "spec_repo_commit": "ba8b66cb"
+            "regenerated": "2025-05-08 14:34:51.506122",
+            "spec_repo_commit": "4b632dba"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-05-07 21:19:51.646277",
-            "spec_repo_commit": "ba8b66cb"
+            "regenerated": "2025-05-08 14:34:51.522046",
+            "spec_repo_commit": "4b632dba"
         }
     }
 }

.generator/schemas/v2/openapi.yaml

@@ -17390,6 +17390,7 @@ components:
       description: The incident severity.
       enum:
       - UNKNOWN
+      - SEV-0
       - SEV-1
       - SEV-2
       - SEV-3
@@ -17399,6 +17400,7 @@ components:
       type: string
       x-enum-varnames:
       - UNKNOWN
+      - SEV_0
       - SEV_1
       - SEV_2
       - SEV_3

lib/datadog_api_client/v2/models/incident_severity.rb

@@ -22,6 +22,7 @@ class IncidentSeverity
     include BaseEnumModel
 
     UNKNOWN = "UNKNOWN".freeze
+    SEV_0 = "SEV-0".freeze
     SEV_1 = "SEV-1".freeze
     SEV_2 = "SEV-2".freeze
     SEV_3 = "SEV-3".freeze