Reset before creating a release metric
What does this MR do and why?
Similar to !2105 (diffs), we should refresh the release status metrics before creating/setting them, so that when they get queried during the metrics
scheduled job and in grafana, the incorrect one simply does not get picked.
This means that we can't "go back in time", but since the metrics are being to display the current status in a text panel in https://dashboards.gitlab.net/d/delivery-release_info/delivery3a-release-information?orgId=1 (similar to the patch pressure metric in the MR above), we don't really need to preserve the metric from before.
This will also address the bug where a release pipeline job (example) runs around the same time as the metrics
scheduled pipeline to refresh the metric (example), and ends up refreshing the older/incorrect release status metric.
Content
- Reset before creating a release metric