Make sure Debian CAL flag bug won't kill my data - restart nut-client on cron

It might be a good idea to run `sudo systemctl restart nut-client` (basically) on cron every hour or something, so that if the UPS runs a self-test, [any machines running Debian 12](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056190) won't get killed off...

Basically:

- [ ] On any Debian 12 system
- [ ] Add a cron job that restarts `nut-client` every hour or every 6 hours...
- [ ] Add a note in the YAML linking back to this issue and/or the Debian 12 bug URL

For the restart, see https://stackoverflow.com/a/49527283/100134 — or could even hack around `systemctl`'s built in functionality here... https://stackoverflow.com/a/50332245/100134

Locate the repository's YAML configuration and deployment entry points, then inspect how Debian systems and nut-client are currently configured. Add the Debian 12 cron-based restart and a YAML note linking to issue #7 or Debian bug 1056190, then verify the generated schedule and service command on Debian 12.

Written by the indexing model from the issue text.