XS✔ ◾ fix: require extractKey when the ExternalSecret is enabled

[dimoschi]

With secrets.externalSecret.enabled: true and no extractKey, the chart rendered key: null under spec.dataFrom[0].extract. The external-secrets.io/v1 ExternalSecret schema requires extract.key as a string, so the API server rejects the resource and the release fails at apply time with a schema error.

The template now uses required, so the same mistake fails at render time with secrets.externalSecret.extractKey is required when secrets.externalSecret.enabled is true. The key is also quoted.

No working config changes: a release that deploys today already sets extractKey. The kubernetes-deploy base sets ${env_name}/services/typesense.

Ported from the same fix in hackthebox/helm-charts#453, made there before the chart moved to this repo.

Tests: added a case for the empty key. mise run test (94/94) and mise run lint pass. No version bump, which is left to the release commit.

[github-actions]

PR Metrics

✔ Thanks for keeping your pull request small.
✔ Thanks for adding tests.

	Lines
Product Code	1
Test Code	10
Subtotal	11
Ignored Code	-
Total	11

Metrics computed by PR Metrics. Add it to your Azure DevOps and GitHub PRs!