Update registering external tools

[andreww-msft]

Summary

Prior to this, you could only register an external tool identified (and activated) by its filesystem path. This PR adds the ability for the user to select a tool from the list of installed apps (both MSIX-packaged and unpackaged). It also supports both launch/command-line activation and protocol activation.

Details

I added a button to the AddTool control to fetch the list of installed apps, based on the list of per-user installed packages and both common and per-user shortcut lists. I also updated the input section for specifying arguments to use variable substitution on a short list of known parameters (initially, just pid and hwnd). This also makes this section more open-ended, as we can easily extend the list later if required.

The user can provide command-line arguments using any format. Protocol arguments should include the protocol itself, and the protocol's Uri.Query can include the standard name-value pairs, or just names. There's no input validation: it's up to the user to provide arguments that are appropriate for her tools. I added tooltips for all the items on the AddTool control, plus instructions and example text for the launch/protocol argument strings.

As part of this, if the user has an externaltools.json file in the old format, we'll read this in and migrate the data to the new format. For persistence, the tools collection is now wrapped in a new ExternalToolCollection type, which includes a version number, so that going forward we can detect files in different versions and migrate accordingly.

Also fixed a bug where we were writing out the JSON file repeatedly when the ToolIcon and MenuIcon observable properties were changed. Now we only write out changes for properties that are not JsonIgnore.

Also added a custom percentage progress ring for reporting intermittent progress when fetching the list of installed apps, as this can take a few seconds. We can also use this progress ring for other long-running operations.

Filed a new issue to support activation via AppExecutionAlias (with arguments): #3251.

Testing

• Tested launch/command-line arguments with unpackaged apps.
• Tested protocol activation with both unpackaged and packaged (both sideloaded and store-deployed) apps.
• Tested migrating an old-format JSON file to the new format.

References and relevant issues

Fixed the following:

• Closes [External Tools] Make the external tools command-line composition more open-ended #3082
• Closes [External Tools] Enable adding an external tool from State Repo and from Uninstall regkeys #3078
• Closes [External Tools] Enable adding an external tool that is protocol activated #3064

[Jason Holmes (jaholme)]

[Zarana Kiran Desai (zadesai)]

[Tim Kurtzman (timkur)]