Test: Turn on Remote Access is aware of existing tunnels

[aeschli]

Test for #171520

• Mac @paulacamargo25
• Linux @rzhao271
• Windows @ulugbekna

Complexity: 3

Create Issue

---

As a follow up work for #171520, now also the Turn on Remote Access handles existing tunnels that have been started before VS Code has started (anticipating that tunnels are running as service)

• start VS Code and turn off existing tunnels:
  • open the context menu on the Account icon in the activity bar. It should show Turn on Remote Access...
  • If it shows Remote Tunnel Access is On, run that command and Turn off Remote Access
• close VS Code, and run a tunnel service from the cli:
  • open a terminal and run code-insiders tunnel, if necessary log in
• open VS Code and open the context menu on the Account icon in the activity bar
  • verify that the menu shows Remote Tunnel Access is On, reflecting the tunnel already started
  • Known bug on Windows, connecting to the tunnel is stuck: Code tunnel: attach does not always work #179122
• in VS Code run the command Remote Tunnel Access is On, run then command Turn off Remote Access
  • Verify that theres a dialog that tells you that stopping the tunnel will also stop the tunnel service started from outside VS Code
  • Verify that stopping also stops the tunnel started from the console

[ulugbekna]

This is really cool!