Port forwarding: when the local port is privileged, offer to elevate and use the privileged port if possible

[alexr00]

Currently, if preferred local port is privileged, we just pick some other available port. Instead, we could offer to elevate and use the privileged port instead. This would allow users who rely on specific privileged port numbers to continue to develop as though everything is local more easily.

[PavelSosin-320]

@alexr The same is for Podman! Only rootfull containers ca map priviledged ports. Rootless can't publish priviledged containers:
Podman networking . The difference is that no priviledged containers. Only Rootfull and rootles. "Randomization" has to take it into account: it has to start from 1024 for rootless users. Only rootfull processes can listen priviledged ports connected to protocols. I afraid it is firewall restriction :( . It affects all my games with Podman. The pre-defined diapazone will be even better because new CNI firewall and portmapper plugins for bridge network driver support it - it is expected.
Please, don't forget to display mapping to user

[visini]

Temporary workaround (execute this on your laptop to relay tunneled port 32798 to port 80 on localhost):

brew install socat # if not already installed
sudo socat TCP-LISTEN:80,fork TCP:$IP_OR_HOSTNAME_OF_REMOTE:32798 # 32798 corresponds to port on remote, which is tunneled to your laptop, e.g., via SSH Remote Explorer UI
curl localhost # this will work now

Looking forward to this functionality!