fix(tor-controller): repoint kube-rbac-proxy after gcr.io takedown (#7)

## Summary

Upstream tor-controller (`tor-controller-0.1.17`) pins
`gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0`, which Google removed from
gcr.io. The sidecar fails with \`ImagePullBackOff\` and
\`gitops-operators\` stays Progressing waiting for the Deployment to go
Healthy.

Override the image via kustomize to the maintained brancz fork at
v0.18.0.

## Test plan

- [x] Live cluster: \`kubectl set image\` to the new ref makes the
Deployment Healthy
- [ ] After merge: \`gitops-operators\` Application reaches Synced +
Healthy

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Author: xnoto

operators/tor-controller/kustomization.yaml

@@ -9,6 +9,13 @@ resources:
 # Override namespace from tor-controller-system to tor-controller
 namespace: tor-controller
 
+# Upstream pins gcr.io/kubebuilder/kube-rbac-proxy which Google removed; re-point
+# to the maintained brancz fork.
+images:
+  - name: gcr.io/kubebuilder/kube-rbac-proxy
+    newName: quay.io/brancz/kube-rbac-proxy
+    newTag: v0.18.0
+
 patches:
   # Fix namespace references in ClusterRoleBinding
   - patch: |