Register restart for resume

[Ryan (ryfu-msft)]

Related to: #3165

Changes:

• This PR calls RegisterApplicationRestart to register winget to restart upon a reboot. The resume command and the resume id are passed as arguments to the winget process so that it can resume from where it left off prior to reboot.
• Registering for a restart will only take place if the result of the installation is REBOOT_REQUIRED_FOR_INSTALL.
• The checkpoint database will only persist if the result of the installation is REBOOT_REQUIRED_FOR_INSTALL.
• Added a new settings value called maxResumes that limits the number of times a resume state can be "resumed". This is to ensure that continuous reboots don't occur.
• In order for the process to be restarted, the reboot must be kicked off while the process is still running. The winget process cannot be terminated normally or else Windows Error Reporting will not initiate the restart. My workaround is to have the process sleep while the reboot process is kicked off.
• Moved the InitiateReboot() flow to take place after --wait argument is processed so that the user is prompted to continue before a reboot is kicked off.

Microsoft Reviewers: Open in CodeFlow

[JohnMcPMS]

If the context is terminated (not with an exception, but "normally"), this code will still run. That may or may not be correct, but I want to make sure it is considered. It feels ok, but then I worry that it won't happen for an exception. I would say that we haven't been strict on the precise method for failures to propagate, which means that this code is likely to not run in some situations when it probably should.

Since this is experimental, it is fine to live here for now. But it will be good to keep this in mind.

[Ryan (ryfu-msft)]

@microsoft-github-policy-service rerun