Runner Registration fails with Operator and Gitlab.com using our instructions

At the moment, OperatorHub has GitLab runner version 15.8 available for installation.

When installing this version and trying to register the runner against GitLab.com project (currently 16.1), it fails with the following error:

12:49 $ k logs pod/gitlab-runner-runner-6d6d7dcccc-vxvzr 
Defaulted container "runner" out of: runner, configure (init)
concurrent = 10
check_interval = 30
log_level = "info"
listen_address = '[::]:9252''/scripts/config.toml' -> '/home/gitlab-runner/.gitlab-runner/config.toml'
Registration attempt 1 of 30
Runtime platform                                    arch=amd64 os=linux pid=11 revision=f86890c6 version=15.8.1
WARNING: Running in user-mode.                     
WARNING: The user-mode requires you to manually start builds processing: 
WARNING: $ gitlab-runner run                       
WARNING: Use sudo for system-mode:                 
WARNING: $ sudo gitlab-runner...                   
                                                   
Created missing unique system ID                    system_id=r_lb5CIHq5rLCp
FATAL: Runner configuration other than name, description, and executor configuration is reserved and cannot be specified when registering with a runner token. This configuration is specified on the GitLab server. Please try again without specifying those arguments.

This happens because we have Adapted the Helm Chart to support the next Token Architecture in 16.0, however, older charts are incompatible with GitLab installations that support new runnerRegistrationToken architecture.

We need to make sure to get the latest GitLab Runner released to OperatorHub asap to fix this issue.

Steps to reproduce are outlined in this comment