publish new images after recent PRs are merged and tested

[szaimen]

Follow up to #3376

(add the most recent ticket for a new release here)

Tested:

(add PRs below that are potentially breaking and need to be well tested)

• adjust docker-lint to use hadolint #3231 (test clamav fixed with 71484bf)
• add warning to notify-push if binary was not found #3398
• drop NET_RAW from all containers #3377 (test if domain still gets accepted on clean instance also test all features?)
• require image_tag and add %AIO_CHANNEL% variable #3314
• remove justinrainbow/json-schema again #3417
• community-containers - add fail2ban as example container for testing purposes #2637 (test that NET_RAW still gets added)
• allow to specify AIO_COMMUNITY_CONTAINERS #3424
• merge containers.json and make sure they depend on the apache container #3425 (fixed detail with 3104d6e and 36baadc)
• adjust limiting the php-fpm port to specific containers again #3427 (check notify push, dsp healthchecks und nextcloud container logs)
• eturnal - set blacklist_peers #3426
• community-containers - add plex #3439
• community-containers - add vaultwarden #3455
• community-containers - add pi-hole #3456 will be tested by community, not a good idea to install on VPS
• apache ip binding - allow ipv6 #3457
• allow to set aio_variables from containers.json #3459 (fixed with overwrite APACHE_PORT, TALK_PORT and APACHE_IP_BINDING only during do… #3482)
• community-containers - add caddy #3460
• only add container to apache container list if display_name is set #3463
• make docker-socket-proxy visible in AIO interface #3469 (fixed with 7fd65f2)
• allow to add documentation on containers #3478 (fixed with add documentation links correctly #3481)
• Revert dbpersistent setting to check if it fixes too many db connections #3479
• Nextcloud dependency update #3420

Tasks to do for new release:

• make sure to merge any Helm Chart Updates PR before continuing with the list below (https://github.com/nextcloud/all-in-one/pulls)
• increase the version number in https://github.com/nextcloud/all-in-one/blob/main/php/templates/containers.twig#L19
• build new images. See https://github.com/nextcloud/all-in-one/blob/main/develop.md#how-to-build-new-containers
• do a last smoke test using the develop channel (See https://github.com/nextcloud/all-in-one/blob/main/develop.md#how-to-test-things-correctly)
• deploy from develop to beta. See https://github.com/nextcloud/all-in-one/blob/main/develop.md#how-to-promote-builds-from-develop-to-beta
• tag a new release here on github which fits the version number (and use vX.Y.Z as tag and title + Beta, use the autogenerated changelog. Important: also add the included Nextcloud version manually into the body of the release, e.g. Nextcloud 26.0.2 is included but new instances can install Nextcloud 27 directly) and make it a pre release
• rename next milestone to the same version number
• create a new milestone that is called next
• move all open issues/PRs to that new milestone
• post in all issues and discussions that were fixed/implemented that this is now released with the new beta version and post how to switch to the beta channel (e.g. This is now released with X.Y.Z Beta. Testing and feedback is welcome! See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel)
• wait a week and see if new bugs get reported and don't merge any PR into the main branch of this repo in the meantime! (until 12.10. or 19.10.)
• if not, publish to latest as describe below; if yes simply close this milestone and create a new one that includes the bugfixes and starts from the beginning of this guide
• deploy from beta to latest. See https://github.com/nextcloud/all-in-one/blob/main/develop.md#how-to-promote-builds-from-beta-to-latest
• Merge the automated YAML updates PR if there should be one (https://github.com/nextcloud/all-in-one/pulls)
• change the pre-release to be a stable and the latest release and remove Beta from the title (and adjust the changelog if multiple Beta version have been pushed in the meantime without a stable release - the changelog must include all changes since the latest stable release)
• close the old milestone