fix(helm): close validateSecret before the new shared-state define

The shared-state guard was added between validateSecret's inner {{ end }}
and the one closing the define, so the new define nested inside it and
the chart stopped parsing: 'unexpected <define> in command'. Neither the
guard nor any other template rendered.

Closes validateSecret first and drops the now-stray trailing end. Checked
with helm lint plus template renders at one replica, at three without
Redis (guard fires), and at three with Redis.

Author: cport1

charts/fcaptcha/templates/_helpers.tpl

@@ -60,6 +60,7 @@ to do by accident, and it costs one line of setup to satisfy.
 {{- if and (not .Values.secret) (not .Values.existingSecret) -}}
 {{- fail "\n\nfcaptcha: a token signing key is required.\n\n  --set secret=$(openssl rand -hex 32)\n\nor point at one you already manage:\n\n  --set existingSecret=my-fcaptcha-secret\n\nWithout it the server falls back to a key published in its own source, and\nanyone can mint tokens your backend will accept.\n" -}}
 {{- end -}}
+{{- end -}}
 
 {{/* Multiple Go pods require shared security state. */}}
 {{- define "fcaptcha.validateSharedState" -}}
@@ -69,4 +70,3 @@ to do by accident, and it costs one line of setup to satisfy.
 {{- fail "\n\nfcaptcha: multiple replicas require Redis-backed shared state.\n\nSet redis.url or redis.existingSecret, or keep replicaCount=1 and autoscaling.enabled=false.\n" -}}
 {{- end -}}
 {{- end -}}
-{{- end -}}