Add resource parameterization for kube-rbac-proxy in stunner-gateway-operator-controller-manager deployment

[towasz]

Currently, the kube-rbac-proxy container in the stunner-gateway-operator-controller-manager deployment does not support resource parameterization. This makes difficult to adjust resource requests and limits based on cluster requirements.

It would be beneficial to allow standard resource parameterization, similar to how it is implemented in stunner-auth.

[levaitamas]

Hey @towasz, thanks for pointing this out.
We are working on removing the unmaintained kube-rbac-proxy from our charts (see #48 and #47) both in the dev version and in the next stable release.
In the meantime, edit our charts locally by adding the missing resource configuration pieces.