[FEATURE REQUEST] Detect when MSI Needs a Reboot

### Please confirm these before moving forward.

- [X] I have searched for my feature proposal and have not found a work-in-progress/duplicate/resolved/discarded issue.
- [X] This proposal is a completely new feature. If you want to suggest an improvement or an enhancement, please use [this template](https://github.com/marticliment/WingetUI/issues/new?assignees=marticliment&labels=enhancement&projects=&template=enhancement-improvement.yml&title=%5BENHANCEMENT%5D+%28Enter+your+description+here%29).

### Describe the new feature

While, for the vast majority of cases, MSI can detect locked files and trigger restarts of the locking processes (called the RestartManager), many MSI's disable this ability, requiring MSI to schedule file updates during the next reboot (likely due to the bad name of the subsystem).

The most common result to end users is the annoying `1603` error code - denoting that a reboot is needed and all MSI's will fail.

It would be nice if UniGet could [detect](https://stackoverflow.com/questions/1685821/how-to-find-out-if-an-msi-i-just-installed-requested-a-windows-reboot/1685861) when the MSI engine needs to reboot (either before attempting to install, or after a `1603` is detected).

### Describe how this new feature could help users

Right now, UniGet exposes much of the complexities of installers directly to users. Most end-users are likely developers, so this isn't horrible, but also not ideal. I would guess most developers don't know how MSI's and general Windows installers work (nor do many want to know 😹).