Druid Operator Relies On Removed gcr.io/kubebuilder/kube-rbac-proxy

Hello,

It seems that the following image doesn't exist anymore:

```
docker pull gcr.io/kubebuilder/kube-rbac-proxy:v0.13.1
Error response from daemon: manifest for gcr.io/kubebuilder/kube-rbac-proxy:v0.13.1 not found: manifest unknown: Failed to fetch "v0.13.1"
```

This container image was still referenced in the default values.yaml overlay of Druid for version 36.0.0:
https://github.com/apache/druid/blob/druid-36.0.0/druid-operator/chart/values.yaml#L39
https://github.com/apache/druid/blob/druid-36.0.0/druid-operator/chart/templates/deployment.yaml#L69

I fear that if the operator is restarted for any reason on a Kubernetes node that doesn't have this image already locally, the Druid operator controller pod will fail because it cannot download the image.

### Affected Version

This doesn't affect users who do not use the Druid Operator.

The Druid operator versions that are affected by this are from v1.2.0 to v1.3.1 if using the old [datainfrahq/operator](https://github.com/datainfrahq/druid-operator).

Version 36.0.0 in this git repository also seems to be affected.

Start with druid-operator/chart/values.yaml at line 39 and druid-operator/chart/templates/deployment.yaml at line 69, then inspect the operator chart's image configuration. Identify a pullable replacement for the removed kube-rbac-proxy image, update the chart reference, and verify that the rendered deployment no longer uses gcr.io/kubebuilder/kube-rbac-proxy:v0.13.1.

Written by the indexing model from the issue text.