Create rolebinding for .Release.Namespace implicitly

[jkremser]

When helm chart is installed with a non-empty watchNamespace field, it will create the RoleBinding resource for the cluster role that contains most of the operator rights for each specified namespace in this CSV field. However, not for the namespace into which we actually install KEDA (mostly called keda).

So this PR adds the .Release.Namespace to the list

Checklist

• I have verified that my change is according to the deprecations & breaking changes policy
• Commits are signed with Developer Certificate of Origin (DCO - learn more)
• README is updated with new configuration values (if applicable) learn more
• A PR is opened to update KEDA core (repo) (if applicable, ie. when deployment manifests are modified) N/A

Fixes #641

[zroubalik]

LGTM, thanks for the fix

[kamialie]

I guess you could also increment patch part of the Helm chart version.

[calvinbui]

i dont think this will solve the problem as the clusterrole is still missing the list and watch actions if .Values.permissions.operator.restrict.secret: true?

https://github.com/kedacore/charts/blob/v2.14.2/keda/templates/manager/clusterrole.yaml#L33-L40

[jkremser]

@calvinbui i think you are right, I've added this in another commit (only for the .Release.Namespace)
@kamialie I'd let the versioning and releasing to the maintainer

[joebowbeer]

How is the documentation regarding restricting access to secrets affected by #625 and this change?

#685 (comment)