Replace dependency script with WinGet Desired State Configuration

Summary

We have automated (via script) and manual steps to install dependencies here.

That script is challenging to maintain, and is located here.

WinGet configure has some capability to standardize this kind of thing: https://learn.microsoft.com/en-us/windows/package-manager/configuration/

Motivation

We don't want to maintain this script. And WinGet likely will need changes to support our complexity and the earlier we engage the more time there is to make fixes.

Open Questions

Our dependency script is complicated as these things go. WinGet might not be ready to replace something of this complexity. But we can start investigating it as a replacement, even if partial.

The normal recommendation for this would be to use the Sandbox to set up the configuration. Because installing Visual Studio is a requirement, the Sandbox would run out of disk space. So we'd need to build the configuration from a base Windows VM instead.

Start by reading vnext/Scripts/rnw-dependencies.ps1 and the dependency instructions at rnw-dependencies. Compare the script's requirements with WinGet configuration support, using a base Windows VM rather than the Sandbox because Visual Studio may exceed its disk space. Done means establishing whether WinGet can replace all or part of the existing setup and recording the resulting configuration or limitations.