Resolve "Update Kyverno Cluster Policy"

General MR

Summary

Currently we have to set up a separate ClusterPolicy to facilitate using another label in order to propagate the secret across all of our runners. The issue with using the default policy that we provide to consumers is that it utilizes the .Release.Namespace which would mean anyone would be forced to essentially either create their own policy or add the label kubernetes.io/metadata.name: "{{ .Release.Namespace }}" (which generally would be gitlabRunner) to each of their runners. We should allow for customization, so I recommend us implementing a value that is customizable and if there is no value, default back to kubernetes.io/metadata.name: "{{ .Release.Namespace }}"

Relevant logs/screenshots

(Include any relevant logs/screenshots)

Linked Issue

#132 (closed)

Upgrade Notices

N/A