[Helm Chart] Allow extra ConfigMap and Secret to be added to gateway chart envVars

[nevarsin]

📝 Description

Allow an external Secret or ConfigMap to be added to the gateway Deployment envFrom.
Current implementation forces secrets to be set in clear text in values.yaml while this PR would enable scenarios where e.g. an existing external Secret Management solution is in charge of creating said Secret.

🔗 Related Issue

Fixes #

🚀 Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🎨 Style/UI update
• ♻️ Code refactor
• ⚡ Performance improvement
• ✅ Test update
• 🔧 Build configuration change
• 🧹 Chore

📋 Changes Made

• Added extraEnvVarsCM and extraEnvVarsSecret elements to values.yaml
• Add conditional insertion of said elements to gateway Deployment.yaml

🧪 Testing

helm template hoop deploy/helm-chart/chart/gateway --values deploy/helm-chart/chart/gateway/values.yaml

Test Configuration:

• Browser(s): Not relevant
• OS: NixOS unstable - Linux 6.17.1

Tests performed:

• Unit tests pass
• Integration tests pass
• Manual testing completed

📸 Screenshots (if applicable)

✅ Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• New and existing unit tests pass locally with my changes
• I have checked my code and corrected any misspellings

📄 Additional Notes

Didn't run unit tests as app logic is untouched.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[nevarsin]

I have read the CLA Document and I hereby sign the CLA

[nevarsin]

Ping