chore: Remove wrapper script for fail2ban service (#3032)

* chore: Remove the wrapper script for `fail2ban`

- This does not appear necessary. The server can be run with foreground mode.
- `daemons-stack.sh` removal of the socket can be handled by the fail2ban server when using the `-x` option.

* chore: Remove `touch /var/log/auth.log`

These were both added as supposed fixes in 2016 for the then Ubuntu 2014 base image.

Removing them causes no failures in tests.

* fix: Install optional python packages for `fail2ban`

These have barely any overhead in layer weight. The DNS package may provide some QoL improvements, while the `pyinotify` is a better alternative than polling logs to check for updates.

We have `gamin` package installed but `fail2ban` would complain in the log that it was not able to initialize the module for it. There only appears to be a `python-gamin` dependent on EOL python 2, no longer available from Debian Bullseye.

target/scripts/wrapper/fail2ban-wrapper.sh

@@ -1,31 +0,0 @@
-#!/bin/bash
-
-# You cannot start fail2ban in some foreground mode and
-# it's more or less important that docker doesn't kill
-# fail2ban and its chilren if you stop the container.
-#
-# Use this script with supervisord and it will take
-# care about starting and stopping fail2ban correctly.
-#
-# supervisord config snippet for fail2ban-wrapper:
-#
-# [program:fail2ban]
-# process_name = fail2ban
-# command = /path/to/fail2ban-wrapper.sh
-# startsecs = 0
-# autorestart = false
-#
-
-trap "/usr/bin/fail2ban-client stop" SIGINT
-trap "/usr/bin/fail2ban-client stop" SIGTERM
-trap "/usr/bin/fail2ban-client reload" SIGHUP
-
-/usr/bin/fail2ban-client start
-sleep 5
-
-# wait until fail2ban is dead (triggered by trap)
-while kill -0 "$(< /var/run/fail2ban/fail2ban.pid)"
-do
-  sleep 5
-done
-