Added support for proxy_ssl_server_name to automate-es-gateway

[mskdenigma]

🔩 Description: What code changed, and why?

When connecting to external Opensearch clusters they may be configured in a way that requires passing along the hostname via the http request. One example of this is Opensearch hosted in Kubernetes which is using a shared ingress that depends on the hostname to be passed for internal routing to the correct service. This code updates the config api to support a new boolean value AND updates the nginx config for automate-es-gateway to check for this config value to determine whether or not to set proxy_ssl_server_name on;

⛓️ Related Resources

👍 Definition of Done

You should be able to set or patch in this config:

[esgateway.v1.sys.ngx.http]
proxy_ssl_server_name = true

and the nginx.conf for automate-es-gateway should include the line

proxy_ssl_server_name on;

👟 How to Build and Test the Change

I need help testing this as attempting to run the dev environment even on the main branch with no changes is failing for me.

✅ Checklist

All PRs must tick these:

• I have read the CONTRIBUTING document.
• All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

• Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
• Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
• Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
• Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
• Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

• Tests added/updated? (all new code needs new tests)
• Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.

📷 Screenshots, if applicable

[netlify]

👷 Deploy Preview for chef-automate processing.

Name	Link
🔨 Latest commit	ea4b9cf
🔍 Latest deploy log	https://app.netlify.com/sites/chef-automate/deploys/64a44e550810e1000835a822

[nrgetik]

fyi @chef/automate-team

[vivek-yadav]

Thanks @mskdenigma for the PR, we will get it Reviewed and Tested by next week.