Description of the new feature / enhancement

Suggestions from one of our very dedicated users:

1. Register for the user (when appropriate) after Repair -AllUsers
   a. While the provisioning step does this eventually, it is not synchronous and can break scripts that want to immediately use winget
2. Ensure that Repair also installs the winget-cli source package. a. This is actually a workaround for an OS issue that prevents winget.exe from installing it in certain scenarios
   b. An alternative solution would be to move away from installing it at all and have all code paths use the unpackaged path (this does have a performance cost though)
3. Fix Win32Exception An error occurred trying to start process 'winget.exe' error the first time Repair -AllUsers is run
   a. Possibly only repros in the headless scenario
4. Repair -Force should bypass checks and attempt to install everything

They also suggest effectively #4390 , but including all PowerShell modules.

Proposed technical implementation details

No response