Specify Dependency Source

[Trenly]

Description of the new feature / enhancement

• Related to [Dependencies] - Manifest validation errors with msstore package identifier #3271

In an enterprise setting, or a setting where custom sources are in play, there is a possibility that Package Identifiers will conflict. Currently, the way to definitively identify a package is through the Source-Identifier pair.

To ensure conflicts are avoided in an enterprise scenario, it should be possible to specify the source to use for a package.
Alternatively, sources to not use could also be specified.

Proposed technical implementation details

There is a complication here that sources can have almost any name. Additional thought may need to be given around how to specify the source details like the type and URL as part of the dependency.

This may also necessitate the need to define a new type of dependency -

Dependencies:
  Sources:
    - <Source Information>

[Trenly]

@stephengillie - can I also request Dependencies and Area-Manifest labels?