Add info command to display key information

[mdanish-kh]

• Have you signed the Contributor License Agreement?
• Are you working against an Issue?
  • Resolves Support wingetcreate --info option #460

This PR adds support for root options for the CLI and the following:

• Support for adding Table output. There were a couple of open-source options available but they weren't stylistically similar to how it is displayed in winget CLI.
• User setting to specify whether paths displayed should be anonymous. This change is for both paths displayed on info command and manifest location showed at the end for update command
• Help text for root options

@ryfu-msft Can you kindly create these short URLs if you approve of them ☺️

https://aka.ms/winget-create-license → https://github.com/microsoft/winget-create/blob/main/LICENSE
https://aka.ms/winget-create-privacy → https://github.com/microsoft/winget-create/blob/main/PRIVACY.md
https://aka.ms/winget-create-3rdPartyNotice → https://github.com/microsoft/winget-create/blob/main/NOTICE.txt

---

Microsoft Reviewers: Open in CodeFlow

[ryfu-msft]

I love everything about having a --info menu similar to winget, but i'm a little hesitant about overriding the command parser to achieve parity. The workaround of appending --help also feels weird to me as it seems to be changing the intended behavior of the library and I don't know what consequences that may have on other things.

I know we should try to align with winget-cli as much as possible but if we can achieve the same end result by simply adding a wingetcreate info command instead, that may be an easier solution. That would also make it easier for testing so we could verify what is displayed. Thoughts?

[mdanish-kh]

I would've loved to keep --info but it looks like anything that I'll do to make that happen will involve me doing a very hacky implementation with the parser. And even then all edge cases may not be covered as was the case with wingetcreate foobar here

I know we should try to align with winget-cli as much as possible but if we can achieve the same end result by simply adding a wingetcreate info command instead, that may be an easier solution. That would also make it easier for testing so we could verify what is displayed. Thoughts?

Sounds good. This will also make it easier in future to implement some common options for all commands (e.g. --log , --open-logs that are mentioned in a couple of issues here) since Info will now be a child of BaseCommand class

[ryfu-msft]

Just a couple more nits and we can get this checked in 😄

I'll start working on getting this aka.ms links ready

[ryfu-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ryfu-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ryfu-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ryfu-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ryfu-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ryfu-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ryfu-msft]

Having some issues with some internal builds, will investigate and check this PR in when it starts passing. Thanks for the awesome contribution @mdanish-kh!

(also, aka.ms links that you mentioned above are all now live)