Implement a friendly way to stop stale environments

The /chatops run rollback check <env> command relies on the status of the deployments associated with the environment to determine the package to rollback to. These deployment entries are handled by our tooling, particularly by the DeploymentTracker class, and are updated and created during the actual deployment performed by the coordinated pipeline.

On some occasions, some of these entries are staled, meaning they will keep the running status indefinitely:

image

gitlab-org/release/docs!425 (merged) introduced a way to fix these stale environments but it requires a rails console access which can be intrusive and prone to errors.

Proposal

Build a rake task on release tools that allow you to update these environments via API https://docs.gitlab.com/ee/api/deployments.html#update-a-deployment