fix(sqs-operator): persistence, OOM, Ingress routing (v0.1.2→v0.1.4)

Problem 1: elasticmq-native does not support H2 JDBC persistence
- GraalVM native build excludes H2 driver
- Fix: switch to softwaremill/elasticmq:1.7.1 (JVM image)

Problem 2: OOMKilled — JVM requires >150MB, spec.MemoryMB=64 too low
- Fix: enforce minimum 256Mi for JVM; add -Xmx (75% of limit)

Problem 3: AccessDeniedException on /data — PVC mounted as root:root
- JVM image runs as uid=999 (elasticmq)
- Fix: add fsGroup=999 to PodSecurityContext

Problem 4: 404 through HTTPS — nginx rewrite stripped context-path
- ElasticMQ JVM listens at context-path (/sqs/{tenantId})
- Native image tolerated /, JVM does not
- Fix: remove rewrite-target annotation, use plain Prefix path

Result: S6 PASS — 8 queues + messages survived graceful pod kill

sqs-operator/internal/elasticmq/elasticmq_config.go

@@ -1,7 +1,7 @@
 // Изменён: 2026-04-07
 // elasticmq_config.go — генератор HOCON конфигурации для ElasticMQ.
 // Каждый тенант получает уникальный конфиг: свой context-path, accountId, persistence.
-// Конфиг монтируется в pod как ConfigMap → /opt/elasticmq/custom.conf.
+// Конфиг монтируется в pod как ConfigMap → /opt/elasticmq.conf (путь из ENTRYPOINT JVM-образа).
 
 package elasticmq