Enable running Microsoft Store Developer CLI commands via a new 'store' subcommand.

[azchohfi]

Fixes #142

[nmetulev]

Awesome. before merging:

• Need to have msstore team review and approve
• Usage docs updated to include store command and link to msstore docs
• Readme updated to include store command in the list of commands
• Add tests
• Should we have a silent install option (install MSStoreCLI if not installed) for things like CI? Or a command to ensure it is installed prior to calling it winapp store ensure-available? The second option seems better to me.

[azchohfi]

• Should we have a silent install option (install MSStoreCLI if not installed) for things like CI? Or a command to ensure it is installed prior to calling it winapp store ensure-available? The second option seems better to me.

We have 3 options:

1. Assume that the command we have is interactive, since it requires accepting the store's EULA (through winget). We are using the winget's "Microsoft Store" source, and that source requires accepting the EULA at first usage.
   Not sure how that works in CI though. Also, this is a solved problem (msstore cli installation in CI), that we might not want to solve again (https://github.com/microsoft/microsoft-store-apppublisher). Its a single line in their yaml file.:

    - uses: microsoft/microsoft-store-apppublisher@v1.2

But we are passing that burden to them, which is not ideal.

2. Add a --silent, or something around these lines, that will just force installation by passing --acept-soure-agreements to winget. This might work.

3. We change the installation method to be similar to what https://github.com/microsoft/microsoft-store-apppublisher does, which means moving away from using winget and using the GitHub release to download the zip of a specific version. We then extract that folder to our "tools" folder within the global .winapp folder, which is a known folder for us, so we just call it. Would also work fine, and this is probably the more complete solution, but is way more work on us.