Address a great bunch of warnings.

So the containers can access the host.

The Nagios plugin doesn't work on the device, it needs a mountpoint.

- Use .pre-commit-config.yaml Git skeleton, updating some hooks.
- Remove the Python linters, there's no Python code or planned to be.
- Remove the pre-commit manifest validate hook, there are no pre-commit
  hooks.
- Remove the yamltool formatter, it's too broad (I need to do something
  about that).
- Specify the Ansible playbooks for the syntax check hook, actually
  check them instead of skipping with no files found.

Cleans up the code a bit, I think. Also, why do host keys or account
keys are good for 4 years but the DH parameters are onl good for 4
weeks? Settle on 1 year for all of them.

- Debian testing and the next Ubuntu LTS (jammy) have Toolbx packaged.
  Use that instead of the binary from toolbox-build. Keep a list of
releases that don't have that it packaged since it should be pretty
static and over time can be removed.
- Instead of checking the distro release, check if there's a Kubic APT
  repo defined (like the assertion does). So we have a single place to
list releases that need that repo. Since the current Debian stable
(bullseye) and the next Ubuntu LTS (jammy) have Podman packaged that
list should be very stable (unless there's another ElementaryOS release
based on Ubuntu Focal before 7.0).
- Rename Toolbox to Toolbx in task names (match the renamed project
  name).

- Update and add more hooks (for new code that's about to be added).
- Address found issues.

New apartment, new internet connection. This time using fiber optics and
a _much_ faster connection. Change the port layout a bit. Change the
queueing a bit too.

The goal is to have all of the infrastructure that goes in building and
maintaining shore.co.il in a single repository. Why? Copy less code and
configuration around, maybe share some more code. Hopefully ease
maintenance. Maybe perform far-reaching changes in a single branch
instead of spreading it out across multiple repos (not really sure about
this).

Now that the Kodi host in running Debian Bullseye.

In case I need access to Nextcloud.

I think, not 100% sure. It's in use for a day now and seems to perform
better but opening new connections is still slow.

So they don't all fire at once. Less stress on each host or on the
entire infrastructure.

For accessing Nextcloud and testing a bunch of things.

- mnpw is now working (enough) so let's put it to use for all of the
  various Nagios-style checks.
- Add the monitoring plugins from monitoring-plugins.org/ for check_apt.
  Now I should get better alerts for pending updates. Regular updates
shuold be just a warning but security updates should be a critical
alert. Let's put it in production and see.
- Now with check_apt handling APT updates, write a small shell script
  for a Nagios-style check for firmware updates.
- And the last part of the updates, update flatpaks silently.
- Refactor of the general maintenance and btrfs-specific tasks.
- Tag the include_tasks tasks with always, so those tasks are always
  included so their tags are also evaluated.
- Remove the apt-transport-https package installation, it's a dummy
  package for apt since Debian Buster and Ubuntu Bionic.

This reverts commit fae72bee. Unexpected
consequences.

Makes the local resolver configuration more involved but I think it's
worth when the router is under heavy load.

- New DNS zone for nehes.co.
- Certificates for *.nehes.co.

command_warning is being deprected, callback_whitelist is being renamed to
callback_enabled.

Change the socket group so it can be accessed from a Toolbox container.