fix: align GOMEMLIMIT with pod memory limits and force fresh image pulls

Go's GC doesn't respect cgroup memory limits on its own, risking OOMKill
under load; set GOMEMLIMIT to ~90% of each deployment's resources.limits.memory.
Also switch imagePullPolicy to Always so :latest tags aren't served stale
from node-local cache after a new push.

k8s/charts/queue-crd/values.yaml

@@ -3,7 +3,7 @@ namespace: sqs
 image:
   repository: forgejo.riotpiao.homelab.com/rock/kafka-management-service-queue-operator
   tag: latest
-  pullPolicy: IfNotPresent
+  pullPolicy: Always
 
 kafkaBrokers: "kmsvc-kafka-bootstrap.sqs.svc.cluster.local:9092"
 redisAddr: "kmsvc-redis-master.sqs.svc.cluster.local:6379"
@@ -15,3 +15,6 @@ resources:
   limits:
     cpu: 500m
     memory: 256Mi
+
+# See management-service/values.yaml's goMemLimit comment -- same reasoning.
+goMemLimit: "230MiB"