Support processing --useHttps flag on Functions applications

[captainsafia]

Description

The Functions host supports passing a --useHttps flag to support binding to https://localhost:* instead of http://localhost:*. This change supports picking up this flag and mapping to a target endpoint with the correct scheme.

There's likely more work to be done here (validate what happens with custom certs, etc.) but this wires up the Aspire-specific things at least.

Conributes to #7150

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Is this introducing a breaking change?
      • Yes
        • Link to aspire-docs issue (please use this breaking-change template):
      • No
        • Link to aspire-docs issue (please use this doc-idea template):
  • No

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

[davidfowl]

We should be supporting both http and https. Does that work with the host?

[captainsafia]

We should be supporting both http and https. Does that work with the host?

AFAIK, the Functions host doesn't support being able to listen on HTTP and HTTPS ports at the same time.

[davidfowl]

I don't know if that is a blocker or not, but the tests are failing. So the idea is that when somebody opts into this they only get https. We ignore this during deployment right?