Move GitLab Operator project out of `gl-openshift` group

Let's consider moving the GitLab Operator project out of the gl-opensfhift group into a non-OpenShift-specific group.

For example: gitlab-org/gitlab-operator

While we're on the topic, this reminds me of a discussion that @WarheadsSE mentioned regarding a group named something similar to cloud-native, which could house the Operator as well as CNG, Charts, etc.

TL;DR

We've discussed, and are going to take actions long-term to consolidate into gitlab-org/cloud-native for all Cloud Native GitLab work (containers, Helm, Operator, components).

This issue will close when we move gitlab-org/gl-openshift/gitlab-operator to gitlab-org/cloud-native/gitlab-operator.

Action items

• Epic to track larger work of consolidation
• Creation of gitlab-org/cloud-native sub-group
  • Locate process / DRI capable of creating the group.
  • Group is created
  • Team granted appropriate accesses
• Transfer https://gitlab.com/gitlab-org/gl-openshift/gitlab-operator to https://gitlab.com/gitlab-org/cloud-native/gitlab-operator
  • sync container registry content to temp
  • delete container registries from origin
  • transfer project
  • ensure permissions of team
  • sync container registry content to final home (using registry-migration.gitlab-ci.yml in https://gitlab.com/gitlab-org/gl-openshift/gitlab-operator/-/merge_requests/165, see details below)
  • delete container registries from temp
• Replace all ENV / token configuration
• Update code references to point to new repository location: gitlab-org/cloud-native/gitlab-operator!167 (merged)

Use temporary CI configuration

https://docs.gitlab.com/ee/ci/pipelines/settings.html#custom-cicd-configuration-path