Configure a port as public in `portsAttributes`

[arcanis]

I'd like to configure a port to always be publicly exposed (for context, it exposes a callback API that third-party webhooks are expected to call; the rest of the application will be kept private on a separate port). It doesn't seem possible at the moment in portsAttributes.

Ref https://github.community/t/can-you-mark-a-port-as-public-in-devcontainer-json/219944 (cc @alexbjorlig)

[gjsjohnmurray]

Also at https://github.com/orgs/github-community/discussions/4068

[alexr00]

If we make remote.portsAttributes a trusted workspace setting then this could be ok. Tentatively assigning to May.

[alexr00]

After further investigation and discussion:

• We should only respect a setting to make ports public when the workspace is trusted.
• Workspace trust does not exist in Codespaces
• There is a concept of repository trust in GitHub.com's Codespaces settings
• There is not a way to read this Codespace repository trust setting

I'm going to table this feature request until we have a way to tell if a workspace or repository is trusted in Codespaces.

In the mean time, I have made several improvements that will reduce friction:

• There's a "Make Public" button on the forwarded port notification in web
• If you make an auto forwarded port public it will stay public for that session (if the port un forwards and the re forwards it will stay public)
• If you make a port that's forwarded by the Codespace public, disconnect, then reconnect, it will reforward as public