Camel-k Operator sharding broken again due to hardcoded name for registry-reader in ClusterRoleBinding

[timmy-mathew-ah]

Bug description

With the fix provided in #6533 it fixed the hardcoded ClusterRole and ClusterRoleBinding issue when dealing with operator sharding apparently this issue has re-surfaced again due to hardcoded names in ClusterRoleBinding of registry-reader in rbacs-common.yaml

This should also the same convention as applied for other RoleBinding and ClusterRoleBindings

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  labels:
    app: camel-k
  name: {{ include "camel-k.fullname" . }}-registry-reader-binding
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: {{ include "camel-k.fullname" . }}-registry-reader
subjects:
- kind: ServiceAccount
  name: {{ include "camel-k.fullname" . }}-operator
  namespace: '{{ .Release.Namespace }}'

I can provide a PR for this fix if this change looks fine.

Camel K or runtime version

v2.11.0-nightly

[squakez]

Thanks for checking. Yeah, the problem is that those new resources were not added to the helm resources, hence, they are not picked up. Please hold on this, as I may be working on some refactoring of those privileges and I will take care to fix it when working on the refactoring.

[timmy-mathew-ah]

@squakez Great thanks for picking this up!