Handle parsing wildcard urls in launch profiles

[davidfowl]

Description

• As part of this change expose TargetHostAddress on EndpointAnnotation which describes the original address that was bound to in both the kestrel endpoint list and the launch profile's application urls.
• Added a test

Fixes #5587

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
    • Link to aspire-docs issue:
  • No

Microsoft Reviewers: Open in CodeFlow

[davidfowl]

cc @davidebbo

[mitchdenny]

What impact does this have around requests that are proxied via DCP? I would have thought that for this to be useful the proxy would need to pass through a host header?

[davidfowl]

What impact does this have around requests that are proxied via DCP? I would have thought that for this to be useful the proxy would need to pass through a host header?

For proxied URLs, I think we could make this useful for DCP by setting the binding address (I think that is supported) to 0.0.0.0 if the input is *. I didn't want to tackle that in this PR though as there are potentially security implications. That said, the behavior now not be what is expected if the url is proxied.

We'll end up with the app binding on all interfaces but the dcp proxy using that port and binding to localhost. It will work but may not have the desired effect.

PS: This is what happens today with kestrel endpoints defined as *. We ignore this for DCP's binding and use localhost.

[davidfowl]

OK I made a change to tell the dcp service about the address.

[davidfowl]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).