DSC v3 in Windows Terminal

Nobody has claimed this yet.

# Description of the new feature/enhancement

I would like to leverage Windows Terminal a DSC Resource so I can specify the way I want Windows Terminal configured. WinGet Configuration could leverage a configuration file to set Windows Terminal up the way I want it.

# Proposed technical implementation details (optional)

Some notes from discussion: Paths in the json file will be **H**ard. If someone's got a relative path in their `settings.json`, well, that just won't work on another machine.

The ideal case here is probably a dotfiles-like experience where we can DSC that folder of fonts, images, and settings.json.

### Crawl
- [x] We can install the Terminal.
- [ ] We can set one or two basic global settings (Theme for example).

### Walk
* We can make some customizations to the settings.json. Maybe use a well-known URL to apply your settings.

### Run
* We can also install fragment extensions the user already has.
* We can install distros, PWSH's etc.

### Sprint
* We can export the current settings.json to a dotfiles-like folder, with images, fonts, etc, and re-write the settings.json to use that path

No source files, tests, or entry points are named. Start by reviewing the proposed Crawl, Walk, Run, and Sprint stages, especially the unchecked global-settings item and the desired DSC Resource behavior. Done would require an agreed scope covering configuration, fragment extensions, distros, and dotfiles-style assets.

Written by the indexing model from the issue text.