publish new images after recent PRs are merged and tested

[szaimen]

Follow up to #3044

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

Tested:

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

• eturnal #2855 (fixed with talk - fix eternal relay-ip #3217)
• add password to FTS #3138
• disable logging for domain-validator.php #3139
• add init to docker run scripts nextcloud-releases/all-in-one#42
• add init flag to all containers #3140
• add check for timezone #3153
• add check for unsupported environmental variables #3154
• change grep command #3171
• try to fix grep syntax for db restore #3174
• Update wording for FTS #3178
• fix notify-push trusted proxies #3181
• mastercontainer - improve healthcheck #3186
• apache - improve healtcheck #3187
• talk - improve healthcheck #3188
• add image_tag to containers definition #3191
• nextcloud - improve healthcheck #3207
• ntofiy-push - improve healthcheck #3208
• Fix OO #3232
• add docker-socket-proxy as option #3235 (fixed with improve some deails with docker-socket-proxy #3242)
• disable selinux for watchtower and docker-socket-proxy #3240
• fix securityopt label disabled #3245
• Bump clamav/clamav from 1.1.1-10 to 1.2.0-1 in /Containers/clamav #3278
• disable docker-socket-proxy temporarily #3284
• improve docker-socket-proxy container #3243 (ipv6 fixed with 305dba3)
• add additinal rules for haproxy #3286 (hc fixed with 8cb1d41 and 900ac14 and 8b9a87b)

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 (check if add docker-socket-proxy nextcloud-releases/all-in-one#43 works)
• 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 07.09.)
• 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 (check if add docker-socket-proxy nextcloud-releases/all-in-one#43 works)
• 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