Fixes #36541 - Update Redis default databases for dynflow and cache

Fixes #33723 - Make dynflow-sidekiq services PartOf foreman.service

By doing so systemd stops all dynflow-sidekiq services before stopping
foreman itself and then starts everything in reverse order on restart.
This circumvents the issue with services being restarted at different...

Fixes #32238 - Bind systemd socket to IPv6

By default foreman.socket binds to IPv4 only. This was done to make
matching it in Puma easier, but it's not really what should be done in
2021 where everything should be dual stack by default.

In aecc3187253ada61a311b5229d215452bd6d67b7 the need for this matching...

Refs #29960 - also set PrivateTmp=true for dynflow-sidekiq

Fixes #29960 - set PrivateTmp=true in foreman.service

Fixes #31431 - Update to Puma ~> 5.1

Puma 5.1 introduced a feature to synthesize binds for systemd activated
sockets. This removes the need to duplicate the FOREMAN_BIND in two
places (foreman.socket and foreman.service).

puma-plugin-systemd is no longer needed since Puma 5.1 gained native...

Refs #30803: Enable unix socket binding

Switches to configure bind and port inside Puma's configuration
to allow Unix socket binding or tcp.

Fixes #30730 - Implement systemd notify support for dynflow-sidekiq

Fixes #29356: Use puma-plugin-systemd to provide systemd notify support

This points to a fork of puma-plugin-systemd maintained by theforeman
organization to ensure this works with Puma 4.

Fixes #30014 - set MALLOC_ARENA_MAX=2 for puma