Deploy to Production Canary as a Seperate Step in the Registry Release Process

Context

2023-05-12: Container registry pulls failing wi... (gitlab-com/gl-infra/production#14260 - closed) was caused by a bug that was difficult to detect with CI. If we had deployed to production canary before production itself, there would have been an additional opportunity to confirm that the new release was working as expected before rolling out fully to production.

Solution

We can achieve this by explicitly setting a registry version here in the same file as we use for production version bumps.