Provide ability to use multiple internal manifest for closed networks

[SunbrightShinobi]

Provide the ability to add additional connections to manifests for internal enterprise apps as well as creating an internal manifest for apps copied to offline networks from internet.

• Use Case 1: A company develops and produces windows applications not for public use but internal or customer only but infrastructure teams wishes to deploy the app internally on corporate network with winget-cli along side public apps from internet.

• Use Case 2: Closed networks or classified systems have no external connections to internet but wish to use winget-cli method for installation of internet based apps or internally developed possibly classified applications

Being able to add connections to additional git repositories and being able to add them individually based on branch name for development and automation. Unknown if there is another format that could be loaded into binary repositories like JFrog Artifactory or something. But the over goal would be similar to docker setup. You can create your own internal docker manifests and just add the connection along side public manifests from docker and rhel.

[megamorf]

Duplicate of:

• Support UNC source #160
• Be able to provide an own feed for offline usage #203
• Support internalized package repositories #213
• third-party repository support #226

[denelon]

Duplicate of #213

[ghost]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!