Gitlab Runner Authentication Token Architecture

Are there any plans for Gitlab-Runner version 18 when the Authentication Token registration method is required over the old Runner Registration Token method? This is a big change for how runners are used with Gitlab.

In the official docs it shows the deprecated fields that do not work with the new Authentication Tokens. Some of those values are currently set in the BigBang Helm Chart and it requires that they be set to literal "null" for the runner pods to start.

"Tags" are one of the deprecated fields that will fail the pod if specified in the Helm Chart. Anyone that has a centralized Gitlab and uses Runners across multiple Kubernetes clusters will no longer be able to have jobs run based on those tags without adding the tags manually in the UI.

The name of the Gitlab-Runner pod in the description field of the Runner in the UI would be a possible solution. However, with the new Authentication Token workflow, the pod name is blank in the UI as specified in this issue that was placed with Gitlab.

Also, the Runner replicas are not allowed to be set any higher than 1 in the Helm Chart.

These changes will require major re-architecture depending on how someone is using Gitlab Runners. What are the plans for BigBang to deal with these upcoming changes? When should we expect support for the Authentication Token in BigBang using the Helm Chart?