Investigate whether we should automatically forward ports based on output

[alexr00]

We can scrape the terminal or other output for things that look like ports to be forwarded. Other extensions do this already, so it might be worth moving to the core.

[gyzerok]

It is great, that you are sharing the work you are doing on GitHub. Personally I very much like following iteration plans for VSCode and Remote Extensions. Thank you!

Would it be possible to give a bit more details in the issues? Sometimes issues seem to make sense for you internally, but I feel that they don't make as much sense for a outsider, which a little bit cuts the whole initiative of you being open with the plans.

[alexr00]

Updated the description!

[alexr00]

To verify, connect to your favorite remote (SSH or containers, not WSL) and run something that causes a host:port (ex: http://localhost:3000/) string to output to the terminal (cloning https://github.com/chrisdias/myUsefulSite works). Open the Remote Explorer Ports view and verify that the port now shows as forwarded. Verify that you can connect to it locally.

[weinand]

Works nicely:

What I don't understand is the "Not Forwarding" section:

Does this mean that a corresponding IP6 address isn't forwarded?

Two (small) issues:

• Port scraping doesn't work with debug console:
  
• The set of port-patterns and the fact that they must be URLs is not obvious: it would be helpful to have this list somehow available in the "Forwarded Ports" view.