feat(helm): Allow a user provided jwt secret

[dacbd]

Type of Change

• New Feature
• Bug Fix
• Documentation
• Performance Improvement
• Test/CI
• Refactor
• Other:

Related Issues

NA

Summary of Changes

Allow for passing in a pre existing secret for the console jwt-secret.

Checklist

• I have read and followed the CONTRIBUTING.md guidelines
• Passed make pre-commit (fmt-check + clippy + test + console-lint + console-fmt-check)
• Added/updated necessary tests
• Documentation updated (if needed)
• CHANGELOG.md updated under [Unreleased] (if user-visible change)
• CI/CD passed (if applicable)

Impact

• Breaking change (CRD/API compatibility)
• Requires doc/config/deployment update
• Other impact:

Verification

make pre-commit

Additional Notes

---

Thank you for your contribution! Please ensure your PR follows the community standards (CODE_OF_CONDUCT.md) and sign the CLA if this is your first contribution.

[dacbd]

Hey rustfs team,

Essentially I want to populate the jwt-secret via external-secrets and the chart doesn't allow for that secret to be externally managed, this allows one to pass a secretName through the chart instead of the secret directly through the values.yaml.

If you want comments to be less verbose I can trim them down.

(commits are unverifed because edits were made from an old laptop and I don't have my yubikey for code signing handy)