Add storage code to create a Dev Drive

[bbonaby]

Summary of the pull request

This is the first of 2/3 PR's that will hook up the Dev Drive functionality in Dev home end to end. Another Bigger one for UI/secondary windows will follow.

This PR is to add the storage code needed to create a Dev Drive. There are 5 stages

1. Creating the virtual disk (no elevation required)
2. Attaching the virtual disk (elevation required)
3. Initializing the virtual disk (elevation required)
4. Creating a partition on the virtual disk (elevation required)
5. Formatting a volume as a dev drive. (elevation required)

Currently the Setupflow doesn't have the elevation process Flor has worked on, for all the elevated parts to work in the app. So validation of the parts that need elevation was done outside of the app.

The Dev Drive manager can now get a list of existing dev drives on the users machine to display with this change.

Detailed description of the pull request / Additional comments

Note for formatting the volume, there are no publicly available AND publicly documented apis to format a volume except using the windows managment instrumentation api's (System.Management in .Net) and the windows infrastructure management apis. Both are in maintenance mode and active development on them has ceased. Due to this I tried to use wmi sparingly where it made sense and used win32 public api's for most of the work.

The flags that were placed into wmi to create a dev drive could possibly be removed depending on how the internal conversions go with servicing on the storage side. We do have a plan in case that happens, but will have more information in april and for now we believe we should be fine to proceed with wmi.

PR checklist

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

[bbonaby]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).