Corrective action: Auto-assign sev 2 to incidents that immediately follow a deployment

Summary

One low hanging fruit here is to auto-assign a severity2 blocks deployments label to these auto-incidents if they correlate with a deployment, this way they would get the attention they deserve and shorten the MTTM; if these incidents found to be unrelated, these labels can be manually removed by EOC.

Related Incident(s)

Originating issue(s): production#16042 (closed)

Desired Outcome/Acceptance Criteria

Incidents that immediately follow a deployment are auto-assigned severity2.

Associated Services

Corrective Action Issue Checklist

• Link the incident(s) this corrective action arose from
• Give context for what problem this corrective action is trying to prevent re-occurring
• Assign a severity label (this is the highest sev of related incidents, defaults to 'severity::4')
• Assign a priority (this will default to 'Reliability::P4' but should match the severity of the related incident)