Mark deployment as bad/failed after the fact

[rhcarvalho]

While the deployment script may have succeeded, a deployment may have catastrophic consequences. Being able to mark a deployment as bad help communicate and prevent operators from rolling back into a deployment that is known to cause issues.

When marking the deployment as bad, it would be thus useful to also include some info like a link to a Sentry issue or a text comment explaining why the deployment is bad.

[rhcarvalho]

This idea sprung out of a conversation with @tonyo and @flub.

[untitaker]

Might want to put this into Sentry releases and integrate with them from Freight instead.