[IMPROVEMENT] Spot-update metadata for installed packages just updated.

### 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 improvement refers to an existing feature. If you want to suggest a new feature, please use [this template](https://github.com/Devolutions/UniGetUI/issues/new?labels=new-feature&projects=&template=feature-request.yml&title=%5BFEATURE+REQUEST%5D+%28Enter+your+description+here%29).
- [x] This improvement is not a bug. If you want to report a bug, please use [this template](https://github.com/Devolutions/UniGetUI/issues/new?labels=bug&projects=&template=bug-issue.yml&title=%5BBUG%5D+%28Enter+your+description+here%29).

### Describe the improvement

I am not certain if this is a regression or a feature request, since I don't know if you intended this UX or not. But it seems like an obvious UX omission.
I'm being initially terse with repro conditions, assuming this to be a base case. If not reproducible — then we might switch to the mountains of logs and all.

So the Installed Packages tab keeps its versions stale until refreshed. You can see the listed version still showing v0.5.3 after updating to v1.1.

Expectation: finishing an update procedure for a given package would trigger spot-update of Installed Packages metadata for the package in question.

### Describe how this improvement could help users

Confusion.

Start from the update procedure and the Installed Packages tab described in the issue, tracing how package metadata is refreshed after an update. Reproduce the update from v0.5.3 to v1.1 and confirm that the package's displayed version updates without manually refreshing the tab.

Written by the indexing model from the issue text.