feat: add Helmfile-managed k8s charts for tasks 10-13

Local charts: kafka-cluster (Strimzi Kafka+KafkaNodePool CRs, 3-replica KRaft
topology, 5Gi memory cap, Longhorn storage, pod anti-affinity), queue-crd
(Queue CRD + queue-operator Deployment/RBAC), management-service
(Deployment/Service/ConfigMap/HPA/Ingress, REST exposed externally via
cert-manager-issued TLS, raw gRPC kept cluster-internal per design.md §7a).

helmfile.yaml.gotmpl + releases.d/*.gotmpl wire strimzi-operator ->
kafka-cluster -> redis -> {queue-crd, management-service} via `needs:`.
Directory is releases.d, not helmfile.d as originally sketched in design.md
section 7b: Helmfile v1 treats a literal "helmfile.d" directory as a special
auto-discovery mode that conflicts with an explicit top-level helmfile.yaml.
Files use .gotmpl (required by Helmfile v1 for {{ }}-templated files) and
each declares its own environments: block, since nested helmfiles don't
inherit the parent's resolved values in this version.

Namespace is sqs throughout. environments/homelab.yaml carries no secrets.
Validated locally via helm lint/helm template (all 3 charts) and
`helmfile -e homelab build` (dependency ordering + value substitution) — no
cluster contact made. Live apply is a separate, explicitly-confirmed step.

k8s/queues/orders-fifo.yaml

@@ -0,0 +1,32 @@
+apiVersion: kmsvc.io/v1
+kind: Queue
+metadata:
+  name: orders-fifo
+  namespace: sqs
+spec:
+  fifoQueue: true
+  visibilityTimeoutSeconds: 30
+  messageRetentionPeriodSeconds: 345600
+  maxReceiveCount: 5
+  deadLetterTargetQueue: orders-fifo-dlq
+  delaySeconds: 0
+  partitionsPerShard: 6
+  minShards: 1
+  maxShards: 8
+  shardSplitThresholdBytesPerSec: 5242880
+  shardSplitCooldownSeconds: 300
+---
+apiVersion: kmsvc.io/v1
+kind: Queue
+metadata:
+  name: orders-fifo-dlq
+  namespace: sqs
+spec:
+  fifoQueue: true
+  isDLQ: true
+  visibilityTimeoutSeconds: 30
+  messageRetentionPeriodSeconds: 1209600
+  maxReceiveCount: 5
+  partitionsPerShard: 6
+  minShards: 1
+  maxShards: 1