Migrate Paid tier images with < 6000 tags to the new registry

This issue is for the gradual rollout of existing image repositories in the paid tier to the new registry. Check out the parent epic for more details on this project. &5523 (closed)

Context

This is part of the work to upgrade and migrate the GitLab.com container registry to a new version backed by a metadata database and online garbage collection (&5523 (closed)). This will be achieved following the gradual migration plan detailed in container-registry#374 (closed).

For the gradual Phase 2 production rollout, we'll split the work into 5 portions, in this order:

  1. GitLab Org: We'll start by testing with some custom-made container repositories under gitlab-org/ and then allow all of its new container repositories to be handled by the metadata DB;
  2. Free Tier: Following the GitLab Org rollout, we will proceed with a general rollout for the Free tier
  3. Paid tier (with less than 6000 tags): After the Free tier, we'll work through a gradual migration of paid customers, excluding major, VIP customers. To start, we'll focus on images with less than 6000 tags.
  4. Paid tier (with more than 6000 tags): Since migrating images with more than 6k tags needs to happen over the weekend, we'll attempt to bundle all of these in one or two more weekends.
  5. Major customer To reduce the risk of impacting users of the GitLab.com container registry that have large amounts of data, a very high activity, or very high availability/stability requirements, we will exclude these from (2) and handle them in this step with a manual gradual rollout, customer by customer.

Task

Perform general rollout for existing image repositories for the Paid tier for images with less than 6000 tags on GitLab.com.

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited by Tim Rizzi