Add Systray helper/support

[shelterx]

Here's an attempt to implement optional systray support as discussed in PR #1333
The current implementation is that systray can be ran standalone or it can be toggled to run from the GUI, the end results are the same, just different ways of doing it.

I tried to keep systray behavior how the users generally expect systray implementaions to behave.
The logic was the hardest part.

EDIT:
Regarding the ruff warnings, it seems like ruff was bumped from 0.15.22 -> 0.16.0.

[shelterx]

Memory usage comparison, it seems to be quite normal compared to a similar tray implementation:

   Process                        | VSZ (Virtual Memory)           | RSS (Physical RAM Used)
  --------------------------------|--------------------------------|----------------------------
   arch-update/lib/tray.py        | 430,016 KB (~430 MB)           | 80,844 KB (~80.8 MB)
   input-remapper-tray            | 679,700 KB (~680 MB)           | 79,744 KB (~79.7 MB)

[sezanzeb]

I'll look at this soon, sorry for the delay

[sezanzeb]

I just pushed tons of changes to fix all ruff issues to main, this should fix the pipeline.

[sezanzeb]

I started this review weeks ago but I think I didn't finish reviewing all the changes back then. I'll make another pass soon, once these are addressed.

[shelterx]

Done. Rebased too, hope it went well... :P

[sezanzeb]

The tray process is logging

08:43:18.500734 7112 tray ERROR groups.py:493: Did not find any input device, possibly due to missing permissions

on my system. Are you in the input group?

My devices submenu is empty and says "No presets configured"

[sezanzeb]

Why is it important to silence discovery prints?

[shelterx]

It's to reduce log spam, not sure if you want it visible during normal operartion.

[shelterx]

logger.update_verbosity is true for systray, what we can do is hide it behind a debug flag?
Though with the dbus change that log will be moved.

[sezanzeb]

I think _poll_state would only be important as long as the menu is open, right? If yes, this would also reduce log spam.

[shelterx]

I'll hold this open for now, I want dbus the change to land first.

[sezanzeb]

How about a .desktop file to autostart the tray?

[shelterx]

What will the user expect?
If we just add it as is with a shortcut, it will always start the tray, however it will disappear when the user closes the GUI IF close to systray is disabled.
Perhaps we should sync that "state" instead, if close to systray is disabled it should never fire up the systray.
And rename it to "Enable systray" instead?

[shelterx]

Are you in the input group?

Yeah, I'm in the input group... and /etc/udev/rules.d/60-uinput.rules sets:
KERNEL=="uinput", GROUP="input", MODE="0660"

It was early on I messed around with input permissions, but I think I added the above myself.
error: No package owns /etc/udev/rules.d/60-uinput.rules