refactor: Update the health check UI sample to use SSL

[Jamie-Clayton]

• Encourage health check samples to be secure by design
• Add .net SSL configurations for sample UI.
• Include the health check JSON endpoint in the sample UI to ensure we have no errors displayed
• Include AllowedHosts in the example.
• Contributes to Update the sample UI project to demonstrate security by default #2245

Special notes for your reviewer:

• Uncovered while enforcing SSL by default on IIS servers in production environments
• Found it difficult to quickly resolve the configuration across multiple build profiles
• Migration from net 6 to 8 uncovered changes to the ports used in v7 used by asp.net.
• Uses conventional commits prefix in commit comments.
• 1861 unit tests run locally with a few hiccups. I'm assuming you need to use the .\build\docker-compose.yml to run them all locally, successfully.
• Tries to improve the code to meet OWASP security recommendations for .net. See "A10 Server-Side Request Forgery (SSRF)" recommendations.

You should set AllowedHosts with host filtering middleware when you want to restrict your ASP.NET Core app to specific hostnames. By defining the AllowedHosts key in your configuration (e.g., appsettings.json), you can ensure that your app only responds to requests from those specific hosts. Requests from other hosts will result in a default bad request (400) response. Keep in mind that this is different from CORS, which controls external origins that can access your app’s resources. If you need to manage cross-origin requests, use CORS; if you want to limit your app to specific hosts, use AllowedHosts.

Does this PR introduce a user-facing change?:
Indirectly, it encourages the use of https in the web browser when running Health Checks

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• Created/updated tests
• Unit tests passing
• End-to-end tests passing
• Extended the documentation
• Provided sample for the feature