hyprpm: target installed instead of running version

[RoootTheFox]

Describe your PR, what does it fix/add?

After updating Hyprland, hyprpm update will still build plugins against the currently running version of Hyprland.
This is a little annoying, because you first have to restart Hyprland and then run hyprpm update for your plugins to be built for the correct version.
This PR makes hyprpm build against the installed version of Hyprland instead of the running version, and shows a popup notification if the running Hyprland version differs from the installed one after updating, telling users to restart Hyprland.

Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)

When I tested it on my setup (Arch) everything worked fine, so no I don't think so. Not sure how Nix handles stuff, but it should work there too I suppose.
I did change the signature of hyprpm's getHyprlandVersion func, but gave it a default value of true that corresponds to the original behavior.

Is it ready for merging, or does it need work?

Should be ready for merging, although if you have any feedback (e.g. UX wise) go for it

[vaxerski]

sooo... essentially then it builds for the installed version right?

We also need a safeguard in enable for this, don't we?

[RoootTheFox]

sooo... essentially then it builds for the installed version right?

yeah.

We also need a safeguard in enable for this, don't we?

i mean, the actual safeguard is in ensurePluginsLoadState which is used by enable too where (from my understanding) the actual plugin loading (and unloading) happens

i suppose a notify would be neat though (like how i have it impld in update)

i'll go and update upstream rq and then impl that