[gitlab-qa] wrong runner image configured

Summary

gitlab-qa was always pulling gitlab/gitlab-runner:alpine image, but actually it was not being used. Instead, docker run was using registry.git lab.com/gitlab-org/gitlab-runner:alpine. That means i have to pull the two images, but one of them was not used.

[Mar 30 2023 09:32:56 UTC (QA Tests)] INFO  -- Executing: `docker pull gitlab/gitlab-runner:alpine-v15.8.3`
[Mar 30 2023 09:32:58 UTC (QA Tests)] DEBUG -- Command output:
alpine-v15.8.3: Pulling from gitlab/gitlab-runner
Digest: sha256:1cd5914eeb7f9f697633bae9a9d5111123f06a83c0f9371f17708f119f594d9d
Status: Image is up to date for gitlab/gitlab-runner:alpine-v15.8.3
docker.io/gitlab/gitlab-runner:alpine-v15.8.3
[Mar 30 2023 09:32:58 UTC (QA Tests)] INFO  -- Executing: `docker network inspect test`
[Mar 30 2023 09:32:58 UTC (QA Tests)] DEBUG -- Command output:
[
    {
        "Name": "test",
        "Id": "6f07ff4c2920477757750970dab32415c398824185f9896f4612a46a6a612250",
        "Created": "2023-03-28T22:15:33.942401059+08:00",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": {},
            "Config": [
                {
                    "Subnet": "172.18.0.0/16",
                    "Gateway": "172.18.0.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {},
        "Options": {},
        "Labels": {}
    }
]
[Mar 30 2023 09:32:58 UTC (QA Tests)] INFO  -- Executing: `docker run -d --rm --network test --name runner-for-project-with-scan-result-policy-7a89ca38f711d9e9  --privileged registry.git
lab.com/gitlab-org/gitlab-runner:alpine-v15.8.3   && docker exec --detach runner-for-project-with-scan-result-policy-7a89ca38f711d9e9 sh -c "printf 'concurrent = 1\ncheck_interval = 0\n\
n[session_server]\n  session_timeout = 1800' > /etc/gitlab-runner/config.toml && gitlab-runner register   --non-interactive --name runner-for-project-with-scan-result-policy-7a89ca38f711
d9e9 --url http://xx.xx.xx.xx --registration-token **** --tag-list secure_report_project-with-scan-result-policy-7a89ca38f711d9e9 --executor shell && gitlab-runner run" `
[Mar 30 2023 09:32:58 UTC (QA Tests)] DEBUG -- Command output:
190a01e8563cf3fa537842c447c0185a7f70d0e99d35925c742970f366c48210
[Mar 30 2023 09:32:58 UTC (QA Tests)] INFO  -- Executing: `docker logs runner-for-project-with-scan-result-policy-7a89ca38f711d9e9`

Steps to reproduce

Use gitlab-qa to run e2e tests that run pipelines. For example: pipelines_for_merged_results_and_merge_trains_spec.rb

Example Project

What is the current bug behavior?

What is the expected correct behavior?

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes