Create idempotent method of deploying the Container Registry

Bring the changes utilized for sidekiq: gitlab-com/gl-infra/k8s-workloads/gitlab-com!183 (merged) and create the same mechanism for deploys geared towards the Container Registry.

• Deploys that do not contain a version for the Container Registry will result in no changes
• Deploys that contain a version will upgrade/downgrade the Container Registry
• If a deploy fails, rolling back does NOT entail the need to revert code inside of k8s-workloads/gitlab-com
• We should attempt to elliminate or reuse existing variables:
  • GITLAB_IMAGE_TAG - should be reused to be able to take any version in place (rename the variable if necessary)
  • For sameness, introduce and migrate to COMPONENT_VERSION - with backward compatability using GITLAB_IMAGE_TAG
  • COMPONENT - or similarly named? - should be utilized to determine which component is to be upgraded
• Bonus points for backward compatibility