feat(uptime): Add additional "incident_status" to snuba results (#386)

Author: evanpurkhiser

examples/snuba-uptime-results/1/failure.json

@@ -19,5 +19,6 @@
   "project_id": 456,
   "retention_days": 90,
   "region": "us-east-1",
-  "environment": "production"
+  "environment": "production",
+  "incident_status": 1
 }

examples/snuba-uptime-results/1/success.json

@@ -16,5 +16,6 @@
   "project_id": 456,
   "retention_days": 90,
   "region": "us-east-1",
-  "environment": "production"
+  "environment": "production",
+  "incident_status": 0
 }

examples/snuba-uptime-results/1/timeout.json

@@ -17,5 +17,6 @@
   },
   "organization_id": 123,
   "project_id": 456,
-  "retention_days": 90
+  "retention_days": 90,
+  "incident_status": 0
 }

schemas/snuba-uptime-results.v1.schema.json

@@ -27,6 +27,12 @@
     "environment": {
       "type": "string",
       "description": "The environment associated with this check"
+    },
+    "incident_status": {
+      "type": "integer",
+      "description": "Indicates this results is part of a detected incident",
+      "minimum": 0,
+      "maximum": 1
     }
   },
   "required": ["organization_id", "project_id", "retention_days"]