Cluster-wide resource naming conflicts from plain yaml install

[kriswuollett]

I attempted to install via the yaml directly https://github.com/actions-runner-controller/actions-runner-controller/releases/download/v0.22.0/actions-runner-controller.yaml as described in the directions. Technically I wrapped it in a no-op kustomize / terraform module to make it deployable like other cluster services I run. However, there appears to be a good possibility for naming conflicts in the cluster-wide resources like the ValidatingWebhookConfiguration and MutatingWebhookConfiguration because the yaml file literally uses the generic transform of the names validating-webhook-configuration and mutating-webhook-configuration. This conflicts with other projects' direct kubectl install methods that use the same naming, like https://github.com/rabbitmq/messaging-topology-operator.

So wouldn't it be a "bug" for this project, and others, to not attempt to use a unique name like actions-runner-controller-${role} by default to cluster-wide resources to avoid conflicts in the released yaml file? It would at least cut down the chance of needing to patch the names with something like kustomize.