fix(fingerprint): prevent sensor timeout on long-running sessions

[JeremieRodon]

Introduces an inactivity timeout mechanism that pauses fingerprint verification after a configurable period (default: 0 second/disabled) when no user input is detected. This prevents some device drivers from disconnecting or disabling the sensor during extended lock sessions.

The verification automatically resumes when user activity is detected (mouse movement, clicks, or keyboard input). The sensor is properly released when paused and re-claimed when resuming.

May fixe #702 though that's unclear as the issue is not well documented

See #955 for more context and history on this PR.

[kylemanna]

Been running this for a few days on Lenovo Slim 7i with flaky goodixtls-55x4 firmware.

Previously it'd pretty much always display a message about timing out, with this it seems to recover most of the time. I suspect the other issues are due to the firmware :-/

After varying amounts of time (1 min - 25 minutes) fprintd disconnects leading to this issue from my initial observations. I set the inactive timeout to 15 seconds to disable the finger print sensor just before hypridle turns off the display again and this works better then ever.

[JeremieRodon]

I took the liberty to rebase the branch on 0.9.5 and I changed the 2 log lines to use the hyprutils logger helper.

[PointerDilemma]

@JeremieRodon needs a clang-format. Otherwise looks ok.

However, I wonder if we should add idle/resume to the auth interface and use the idle-notify wayland protocol to trigger those methods.
The benefit of that would be that one, I think the lid-switch counts as an idle event on the compositor level and that would allow a user to open the laptop and use the fingerprint sensor right away; two, some pam usages might also benefit from such and idle mechanism.