feat: Add sni related config options to jwt policy

[javorszky]

Proposed changes

Adds two new configuration options to the NIC / jwt policy options: sniEnabled and sniName.

Functionality PR for the underlying code is nginx/kubernetes-ingress#7993.

⚠️ Does not need to go live until the release that will have 7993 in it (5.2.0 probably)!

Checklist

Before merging a pull request, run through this checklist and mark each as complete.

• I have read the contributing guidelines
• I have signed the F5 Contributor License Agreement (CLA)
• I have rebased my branch onto main
• I have ensured my PR is targeting the main branch and pulling from my branch from my own fork
• I have ensured that the commit messages adhere to Conventional Commits
• I have ensured that documentation content adheres to the style guide
• If the change involves potentially sensitive changes¹, I have assessed the possible impact
• If applicable, I have added tests that prove my fix is effective or that my feature works
• I have ensured that existing tests pass after adding my changes
• If applicable, I have updated README.md

Footnotes

1. Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content. ↩

[github-actions]

✅ Deploy Preview will be available once build job completes!

Name	Link
😎 Deploy Preview	https://frontdoor-test-docs.nginx.com/previews/docs/795/

---

[ADubhlaoich]

Changes LGTM: if these are intended for an upcoming release, we could probably set-up the new release branch so that can be the target instead of main.

Otherwise, I'm somewhat inclined to keep this in draft just in case someone merges prematurely.

[javorszky]

Otherwise, I'm somewhat inclined to keep this in draft just in case someone merges prematurely.

Excellent suggestion, thank you. I need to figure out how to not forget about this draft PR though 🤔