Fix some issues around port forwarding:

[davidfowl]

Description

• Make sure there aren't duplicate labels when written to settings files

• Mark auto forward action for dashboard as open browser and other endpoints as silent.

• Default to hybrid mode for auto port forward. We want to detect ports from the output, but we also want to tear down the portforward when the process dies.

Fixes #7147
Fixes #7148

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

[mitchdenny]

Looks good. Tested it and is very responsive to port changes. Would be good to avoid the pause but we'll need to wait to hear from the VSCode team.

[mitchdenny]

One thing we might want to consider is whether the port label needs some kind of apphost prefix to make it unique per apphost. in theory someone can two two apphosts within a Codespace just fine.

[davidfowl]

Looks good. Tested it and is very responsive to port changes. Would be good to avoid the pause but we'll need to wait to hear from the VSCode team.

Sleep always works 😉

One thing we might want to consider is whether the port label needs some kind of apphost prefix to make it unique per apphost. in theory someone can two two apphosts within a Codespace just fine.

I was going to do that (put the apphost name in there as a suffix), but then we would need to attempt to clean up the file. It turns out the VS debugger does not gracefully exit the process so there's no change to clear the file. It could be done on the next run though.

[davidfowl]

Failures unrelated to the this (cosmos db)

[davidfowl]

Oh one other idea I had in general was to clean up finish modeling the dashboard cleanly as a resource. That would fix a few things:

• Logic to add endpoints would be in a single place
• We could use health checks to wait until the endpoint is valid (codespace health check)

[mitchdenny]

🤔