Improve discoverability of Continue On

[joyceerhl]

Experiment with options, UX sync and additional user studies
- SCM viewlet
- Explorer title menu?
- Have it be its own category in the remote indicator
- Run menu?

[joyceerhl]

Explored some options here:

SCM action button secondary action

SCM view

Note we also already expose Continue On in the welcome views in the terminal and debug view containers

And there is also #162259 to improve discoverability on desktop

[stevencl]

It is worth thinking about how we can bring in the concept of edit sessions (or whatever we call them) during this experience. I think it is important to grasp this concept to understand how it is possible to continue working on another device.

It will be even more important to get this right if we do a good job of telling people that their changes are stored in local storage.

Maybe we need to consider exposing the edit sessions/remote hub immediately on first launch of vscode.dev. Maybe we have the explorer in the top and the remote hub underneath. We show the edit session corresponding to the current session and commands available on that (continue working on etc...)

I like the panel in the SCM viewlet in the mockup above but as we discussed during the UX call I think we need to think about how we can use this to get people familiar with the concept of an edit session so that they might then think about accessing that session elsewhere. That would also provide further motivation for signing in so that they can use these.

[joyceerhl]

Continue On options are now integrated into the remote indicator, command palette, SCM action button dropdown, and terminal welcome view, thus closing.