[BUG] UniGetUI crashed after doing upgrade i did not ask for

### Please confirm these before moving forward

- [x] I have searched for my issue and have not found a work-in-progress/duplicate/resolved issue.
- [x] I have tested that this issue has not been fixed in the latest [(beta or stable) release](https://github.com/marticliment/WingetUI/releases/).
- [x] I have checked the [FAQ](https://github.com/marticliment/WingetUI#frequently-asked-questions) section for solutions.
- [x] This issue is about a bug (if it is not, please use the [correct template](https://github.com/marticliment/WingetUI/issues/new/choose)).

### UniGetUI Version

3.1.7

### Windows version, edition, and architecture

Windows 10 Pro

### Describe your issue

I was upgrading other packages, 4 ones, all of them, as small as clink and as heavy as MSVC++ Build Tools

I noticed UniGet 3.1.6 has shown me a banner about upgrade to 3.1.7

I could've clicked the banner, hopying to see more info or some kind of menu, or maybe i did not, but i certainly did not click the BUTTON on that banner. I "marked" to myself to update UniGetUI later, after heavy and slow MSVC++BT completes.

Then i suddenly saw UniGet's user elevation dialog. I thought this could be some secondary elevation request inside MSVC++BT upgrade process, or something. Then it confusingly popped up UniGUI updater i did not ask for. I remember worrying if it would be okay to update UniGet itself while it was busy updating MSVC++BT. But i trusted UniGet to do what it wants and let it follow.

After that process complete i noticed i do not have UniGet's tray icon any more, i checked there was no UniGet process in Task Manager, i clicked the Start menu icon to recreate it - but to no avail. I clicked the desktop icon - to no avail. I copied the path from the desktop icon and pasted it into cmd.exe hoping to at least get any StdErr.log - there was none, but the UniGet did not start either.

Eventually i just launched "C:\Users\XXXXXX\AppData\Local\UniGetUI\UniGetUI Updater.exe" - and after that UniGet finally could start. The start was very slow, though, like it never was run before and had to rebuild all its databases or something.

There is somethign quite shaky in this UniGet 3.1.6 to 3.1.7 update routine...

### Steps to reproduce the issue

_No response_

### UniGetUI Log

```text
n/a

AFTER it started there is no relevant log

there also was no log-looking files in `AppData\Local\UniGetUI` or i failed to notice it
```

### Package Managers Logs

```text
n/a
```

### Relevant information

_No response_

### Screenshots and videos

_No response_