Signer recognizes annotation prefix for Command metadata and Role/RoleBinding permissions are audited

[m8rmclaren]

The Command Issuer for cert-manager now recognizes K8s annotations with prefix metadata.command-issuer.keyfactor.com/, and adds <metadata-field-name>: <metadata-value> fields corresponding to metadata.command-issuer.keyfactor.com/<metadata-field-name>: <metadata-value> annotations in POST requests to Command for CSR enrollment.

Specifically, the Metadata map is updated with matching annotations at the time of signing:

for metaName, value := range s.customMetadata {
    k8sLog.Info(fmt.Sprintf("Adding metadata %q with value %q", metaName, value))
    modelRequest.Metadata[metaName] = value
}

Additionally, the rules configured on the leader-election-role were audited and the following rule was removed:
https://github.com/Keyfactor/command-cert-manager-issuer/blob/4be4d38bba9395663c38ca85689887596834afe5/deploy/charts/command-cert-manager-issuer/templates/role.yaml#L8C1-L19C15

In early Kubernetes deployments before the coordination.k8s.io group existed, configmaps were commonly used for leader election, whereby obtaining a lock on a specific ConfigMap, a controller instance designates itself as the leader. This is no longer necessary, so the configmap rule was removed.