Implement scope override and scope detection from installer URL

[ryfu-msft]

Currently there is no way for winget-create to detect the scope of an installer. This PR adds the override functionality to allow users to specify the intended scope of the installer to improve matching performance during updates.

Changes:

• Users can now append |user or |scope to the installer URL to specify the scope they want.
• Changed the behavior of installer matching logic. If an architecture override is specified, then that is the architecture used for matching. If no match is found, winget-create does not fallback to the detected arch from either the URL or binary. I believe if the user specifies the override, this is the intended architecture that they want to use for matching.
• Added scope detection based on parsing the installer URL.
• Refactor matching logic for simplicity.

Tests:

• Verifies scope override works as expected
• Verifies scope can be detected from the installer URL

Microsoft Reviewers: Open in CodeFlow

[mdanish-kh]

ArchitectureOverride_Warning Resource string may also need to be updated. An updated message may be something like:

If the installer you provided fails to match an existing installer even when overriding the architecture, you may need to override the scope or edit the existing manifest manually. Make sure that the existing manifest has a single installer that matches the overriding architecture, scope and installer type of the new installer. To modify an existing manifest, use the '--interactive' flag with the update command and submit the new changes. Once the changes are published, please try again.

[yao-msft]