Migrate CustomersDot Ansible to gitlab-org

This issue provides a checklist that will support the migration of [the CustomersDot Ansible project](https://gitlab.com/gitlab-com/gl-infra/customersdot-ansible) to the `gitlab-org` group.

## Main information

- Date and time of migration: November 3rd 2022, 10am UTC (duration: 1 hour)

- Former project URL: https://gitlab.com/gitlab-com/gl-infra/customersdot-ansible
- (Proposed) New project URL: https://gitlab.com/gitlab-org/customers-ansible

- CustomersDot Documentation MR: https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/5520
- CustomersDot Ansible Documentation MR: https://gitlab.com/gitlab-com/gl-infra/customersdot-ansible/-/merge_requests/316
- Runbooks MR: https://gitlab.com/gitlab-com/runbooks/-/merge_requests/5019
- CustomersDot `.gitlab-ci.yml` MR: https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/5522

## Checklist

### Preparation

1. [x] Make sure that someone in the Fulfillment team can proceed to do [the project transfer](https://docs.gitlab.com/ee/user/project/settings/index.html#transfer-a-project-to-another-namespace). We need someone who's both the Owner of `customersdot-ansible` and has the `Maintainer` role for the `gitlab-org` group.
    - Access request issue: https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/issues/18088

1. [x] Prepare the following MRs. Get them approved and ready to be merged, but **do not** merge them.
    1. [x] Prepare an MR to update all CustomersDot Ansible references in the documentation (ie. `README.md`, `doc/` folder, comments) for both the CustomersDot and the Ansible projects.
    1. [x] Prepare an MR that updates all CustomersDot Ansible references in the Runbooks project.
    1. [x] Prepare an MR that updates CustomersDot Ansible references in CustomersDot's `.gitlab-ci.yml`

1. [x] When items above are completed, choose a date and time to do the transfer and announce it in the `#s_fulfillment` Slack channel.

### Project transfer!

1. [x] Create a [new CustomersDot issue](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/new) with a ~"production::blocker" label.
    - Use this issue: https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/5092

1. [x] Create a [new CustomersDot Ansible issue](https://gitlab.com/gitlab-com/gl-infra/customersdot-ansible/-/issues/new) with a ~"provisioning blocker" label.
    - Use this issue: https://gitlab.com/gitlab-com/gl-infra/customersdot-ansible/-/issues/162

1. [x] Delete all existing images: https://docs.gitlab.com/ee/user/packages/container_registry/index.html#limitations
   1. [x] Double-check the current version of [Docker images in the former project](https://gitlab.com/gitlab-com/gl-infra/customersdot-ansible/container_registry) and take note of them:
      - customersdot-ansible: `v0.0.1`
      - molecule-environment: `v0.0.1`

1. [x] Proceed to [transfer the project to `gitlab-org`](https://docs.gitlab.com/ee/user/project/settings/index.html#transfer-a-project-to-another-namespace).

1. [x] Rebuild the Docker images and push them
   1. [x] Make sure you're logged in to the new (migrated) project's registry.
   1. [x] Rebuild Docker images locally (verify version numbers) and push them to the new project's registry:
       ```bash
       # customers-ansible image
       docker build --no-cache -f Dockerfile -t registry.gitlab.com/gitlab-org/customers-ansible:v0.0.1 .
       docker push registry.gitlab.com/gitlab-org/customers-ansible:v0.0.1

       docker build --no-cache -f Dockerfile -t registry.gitlab.com/gitlab-org/customers-ansible:stable .
       docker push registry.gitlab.com/gitlab-org/customers-ansible:stable

       # molecule-environment image
       docker build --no-cache -f test/docker/molecule-environment/Dockerfile -t registry.gitlab.com/gitlab-org/customers-ansible/molecule-environment:v0.0.1 .
       docker push registry.gitlab.com/gitlab-org/customers-ansible/molecule-environment:v0.0.1

       docker build --no-cache -f test/docker/molecule-environment/Dockerfile -t registry.gitlab.com/gitlab-org/customers-ansible/molecule-environment:latest .
       docker push registry.gitlab.com/gitlab-org/customers-ansible/molecule-environment:latest
       ```

### Post-transfer tasks and tests

1. [x] Merge the CustomersDot `.gitlab-ci.yml` MR.

1. [x] Test new configuration:
    - [x] [Provision manually](https://gitlab.com/gitlab-com/gl-infra/customersdot-ansible/blob/8873ad26f8c025db03d86a5fd527dc58d7c64fa0/doc/readme.md?plain=0#manual-provisioning).
    - [x] [Deploy manually](https://gitlab.com/gitlab-com/gl-infra/customersdot-ansible/blob/8873ad26f8c025db03d86a5fd527dc58d7c64fa0/doc/readme.md?plain=0#manual-deployment-to-production).

1. [x] Review that existing CustomersDot Ansible issues, epics, etc, can be found.

1. [x] Close the ~"production::blocker" CustomersDot issue.

1. [x] Close the ~"provisioning blocker" CustomersDot Ansible issue.

1. [x] Ask everyone in `#s_fulfillment` to update their project remote:
    ```bash
    # cd into local customersdot-ansible project
    git remote remove origin
    git remote add origin git@gitlab.com:gitlab-org/customersdot-ansible.git
    ```
    Let them know that deployments have resumed as well.

1. [x] Merge the two Documentation MRs.

1. [x] Merge the Runbooks MR.

1. [x] Apply ~"group::fulfillment platform" to all issues that are already tagged with the ~"Fulfillment::InfraDev" label.

Story points: 2.0