Summary of the pull request

This is PR 3 of 4 to add the ability to create environments from within Dev Home. I currently have 2 other PRs:

• Add ability for Dev Home to display settings cards from an adaptive card #2488
• Add Hyper-V settings card styled adaptive cards  #2489

That will go into a feature branch before going into main. Please look at those for context. This PR adds the Create Environments flow to the machine configuration tool. It utilizes adaptive cards that are retrieved from a Dev Home extension to display the provider specific UI to the user. There are 3 pages:

1. The Select environments page (no adpative card) where the user can select a provider from a list of providers in an items view control
2. The configure environment page where we display the first adaptive card from the extension. This page is used as a "Form" where the extension can send Dev Home its creation form and the user can enter their details/options the provider can use to create the environment.
3. The review page. This is the same review page experience that we have in the machine configuration flow today, however the create environment review tab retrieves the extensions review page adaptive card which is displayed in the tab. See the following video:

We use weak references to send messages between the view model and the views to allow the views to be disposed once they are unloaded. The DevHome Settings card adaptive card control (added in PR #1 above) is used by the Hyper-V extension, to display the list of images that can be used to create a VM just like Hyper-V quick create window.
.

References and relevant issues

• This adds the changes needed up until the user selects the setup button. The next PR will finish the flow by adding code for the loading page, the summary page and the Environments management page where we'll show the status of the environment creation.

Detailed description of the pull request / Additional comments

Note: The use of the ExtensionAdaptiveCardPanel for this kind of wizard flow causes random xaml crashes due to an exception where xaml sees a control being parented to multiple other controls. So it was not used for this feature

Validation steps performed

PR checklist

• Closes #xxx
• Tests added/passed
• Documentation updated