Explore creating a Helm Chart to encapsulate the Runner Helm Chart to provide legacy support for runner configuration

In a discussion with Kamil, he suggested the possibility of creating an outer helm chart to support the legacy scenario where users want to be able to create a ad-hoc runner configuration to execute a job, in the same way that was possible with the registration token. The values.yaml would take a PAT and the runner configuration values, such as tags, protected state, etc.

This would allow users who are reluctant to implement a workflow based on our Terraform provider and want to stay with vanilla Helm chart, to preserve the current behavior. Example.