Allow registration token to be in kubernetes secret
The helm chart user has to specify the Runner registration token in the values.yml. This can be problematic if you want to version control the
values.yml having secrets unencrypted in git is never a good idea. This would be dangerous if the token is for shared Runners because that would mean that anyone with Git access to the
values.yml can take that shared Runner token and use it for malious reaosns.
Create a new field
runnerRegistrationTokenSecretName which would be the name of the Kubernetes secret which can work very similar to certsSecretName where the user specifies the name of the secret of where the registration token is and we will get that secret only during the runtime of the regression command.