hyprsunset: recommend uwsm users to enable as a service

[blakeplusplus]

I personally use uwsm to launch directly into hyprland, where I use both hypridle and hyprsunset. Per the wiki, I have hypridle enabled as a user service (since it recommends that for uwsm users).
Here is my hypridle.conf:

listener {
    timeout = 600
    on-timeout = hyprctl dispatch dpms off
    on-resume = hyprctl dispatch dpms on
}

If I start hyprsunset via hyprland.conf (exec-once = hyprsunset), upon resuming from idle, I get an error stating "could not connect to socket" if I use any hyprsunset temperature changing commands. I have to manually launch hyprsunset for the error to resolve.

I'm able to fix this issue by instead removing exec-once = hyprsunset from hyprland.conf and instead adding it as a service, per the wiki. After rebooting, I'm able to idle and come back from idle with hyprsunset still working.
My problem is that the wiki should recommend uwsm users to launch hyprsunset as a user service for uwsm users like it does for hypridle instead of just saying it's an alternative to avoid this issue. Hope that makes sense.

[fufexan]

Honestly I see no reason to launch services with exec-once, when user services exist.

If you think you can write a quick PR, I can take a look.