publish new images after recent PRs are merged and tested

[szaimen]

Follow up to #2407

(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 the button color on focus #2416
• mastercontainer - delete things except the needed php dir #2431
• add apparmor_unconinfed to containers definition #2432
• collabora - make startup faster by not generating ssl cert #2446
• run composer during install as non-root user  #2459
• Bump clamav/clamav from 1.0.1-2 to 1.1.0-1 in /Containers/clamav #2465
• revert disabling FTS if on Nc26 #2470 will be tested by myself when really upgrading to 26
• nextcloud-aio network - remove non-default options #2482
• talk - remove lt-cred-mech as that is not recommended anymore #2485
• try to speed up the initial login #2488 (fixed with 8750bd3)
• twig templates - check for was_start_button_clicked instead of empty … #2489 (fixed with b08b59b)
• optimize borg dockerfile #2491
• optimize clamav Dockerfile #2492
• optimze domaincheck Dockerfile #2494
• optimze elastic Dockerfile #2495
• optimize redis Dockerfile #2499
• optimize talk Dockerfile #2500 (fails to build currently)
• optimze watchtower Dockerfile #2501
• 93cec3c

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) 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! (at least until 10.05.)
• 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
• close the old milestone