Update Editor to include "Launch & Edit" Flow

[plante-msft]

Update Editor with "Launch & Edit" button that allows users to re-enter the Capture/Create experience from an existing project.

• Launches project and re-enters the standard capture experience.
• Flyout dialogue on click warns user that this will launch project. Can be permanently dismissed.
• Revert option after re-capture restores project to original state (pre-changes).

cc @crutkas @hamza-usmani

[hamza-usmani]

Notes:

• In the preview container: I received some feedback from folks that the preview container with the app layout seems like something users can interact with (ie. move the app icons inside to reposition). We should make it clear in the UI that it is in fact just a Preview of your desktop (perhaps a "preview" title on the container or similar)
• I'm assuming the warning dialog will not show up inside the preview container and that is just mockup positioning, correct?
• Do we want "Launch and Edit" to be disabled after the user edits once? I believe we do not and this is just a mockup

[plante-msft]

Notes:

• In the preview container: I received some feedback from folks that the preview container with the app layout seems like something users can interact with (ie. move the app icons inside to reposition). We should make it clear in the UI that it is in fact just a Preview of your desktop (perhaps a "preview" title on the container or similar)
• I'm assuming the warning dialog will not show up inside the preview container and that is just mockup positioning, correct?
• Do we want "Launch and Edit" to be disabled after the user edits once? I believe we do not and this is just a mockup

• I think it's fine to throw a small "Project Preview" label in the preview window. This doesn't appear to over-clutter the UI in the mocks (see below)
• Yes the warning dialogue is a pop-up flyout that users can reposition by click+drag
• This is done to allow users to Revert to the previous capture. We could leave it permanently enabled but would then have to handle either a) multiple reverts which iterate through the past N captures, or b) communicate to users that clicking reverts to the original, last saved capture. IMO this isn't necessary for MLP.