Implements #1488

## Change
Adds the concept/value of priority to sources. This is an integer value
(default 0) where greater numbers are sorted first. This is an editable
value of a source. Priority has been added to the following interfaces:
1. CLI commands (`source` `add`/`edit`/`list`/`export`)
2. DSCv3 `source` resource
3. DSCv2 source resource
4. Configuration export
5. COM source Add and Edit functionality
6. PowerShell source objects
7. Group policy JSON

Sources are sorted by priority in the list of sources, which has minor
effects such as changing the order in `source list` and the order of
available sources when constructing the default composite source. That
default composite ordering has always had the effect of making equal
match type/field results dependent on the order, but now the priority
can affect the third order sorting.

The larger effect is when multiple sources return results for an
operation targeting available packages (ex. `install`). In this case, if
there is only one result amongst the sources at the highest returned
priority, then that will be used instead of producing an error about
multiple results. For example, if all sources return one result and the
priorities are { Source A = 2, Source B = 1, Source C = 0 }, then the
result from Source A would be installed without any additional user
input (although a warning is output to indicate this has happened). But
if the priorities are { Source A = 2, Source B = 2, Source C = 0 }, then
an error similar to the existing one will be presented with only the A
and B source results.

### REST match criteria
A TODO has also been resolved in the REST source code that evaluates the
match criteria of REST results so that they may be sorted properly
amongst the winget-pkgs results. Previously they were always using
default values (0s) which would cause them to be sorted first.

## Change
Put the localization suggestions from a few PRs into comments on the
en-us version that goes through the localization process.

---------

Co-authored-by: Flor Chacón <14323496+florelis@users.noreply.github.com>

Conclude finished v1.11, add missing v1.12, update vNext reference to
current v2.0 name.

<!-- To check a checkbox place an "x" between the brackets. e.g: [x] -->

- [x] I have signed the [Contributor License
Agreement](https://cla.opensource.microsoft.com/microsoft/winget-pkgs).
- [ ] I have updated the [Release Notes](../doc/ReleaseNotes.md).
- [ ] This pull request is related to an issue.

-----

###### Microsoft Reviewers: [Open in
CodeFlow](https://microsoft.github.io/open-pr/?codeflow=https://github.com/microsoft/winget-cli/pull/5824)

## Change
Add a `--no-progress` common argument that does the same thing as
`progressBar: disabled` in the settings.

## Change
Fix the casing when the term is used to describe the product (WinGet)
while leaving casing when the term is used for the command line
(winget).

The current documentation on the priority orders of installer types when
using `winget install` without having specified `--installer-type`, was
unfortunately pretty scarce. So I've filled in most of the gaps now.

Add additional diagnostics on the starting the DSC process.
Use stable DSC while waiting for
PowerShell/DSC#1420 to be released.

…6071)

In an effort to investigate some SQLite compression improvements, this
tool was created and some changes were made to that are being left as a
null result.

The investigated changes both increased the compressed file size:
- Increased page size to maximum
- Move the package hashes to their own table

## Change
Adds an option that only installs dependencies (command line only
currently).