MR: Pending <!--The first line of this issue description must be one of the following: 1. `MR: Pending` 2. `MR: <MR link with trailing +>`, 3. If there are multiple MRs: ``` MRs: - <MR 1 link with trailing +>` - <MR 2 link with trailing +>` - ... ``` 4. `MR: No MR` ...and the first description line of the MR should be `Issue: <Issue link with trailing +>` For more context, see: https://about.gitlab.com/handbook/engineering/development/dev/create/ide/index.html#relationship-of-issues-to-mrs--> <!--The following sections should be filled out as part of the refinement process before the issue is prioritized. For more context, see: https://about.gitlab.com/handbook/engineering/development/dev/create/ide/gitlab#2-pre-iteration-planning-meeting--> ## Description As a user or stakeholder, I want a list of ports that are running in my workspace so that I can easily click on it to copy/open the URL.  Furthermore, opening ports in a Workspace and removing the Authentication layer(as described in https://gitlab.com/gitlab-org/gitlab/-/issues/471058+) entails security risks. It would be great if we could open and close these ports from the Workspaces UI in VSCode using the "Forwarding ports" panel: ## Acceptance Criteria - [ ] The ports tab will display the following: * [ ] A list of all available ports * [ ] The URL for each corresponding port on the list * [ ] ~~The visibility of the ports listed~~ --\> see [discussion here](https://gitlab.com/gitlab-org/gitlab/-/issues/509815#note_2273083804) for removal of this AC ## Technical Requirements TODO: Fill out or delete (optional) \[If applicable, please list out any technical requirements for this feature/enhancement.\] ## Design Requirements TODO: Fill out or delete (optional) \[If applicable, please provide a link to the design specifications for this feature/enhancement.\] ## Impact Assessment TODO: Fill out or delete (optional) \[Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole.\] ## User Story TODO: Fill out or delete (optional) \[Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality.\] <!--Replace with other type, e.g. bug or maintenance, if appropriate--> <!--Replace with other subtype if appropriate--> <!--By default, all issues start in the unprioritized status. See https://about.gitlab.com/handbook/engineering/development/dev/create/ide/#-remote-development-planning-process--> <!--For simplicity and to avoid triage bot warnings about missing workflow labels, we will default to issues starting at the refinement phase-->