publish new images after recent PRs are merged and tested

[szaimen]

Follow up to #2600

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

Tested:

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

• allow to adjust borgs retention policy #2428 (fixed with bd55031) (test by setting to value on new instance)
• allow to define nextcloud_exec_commands in containers definition #2454
• optimize nextcloud Dockerfile #2497 (test on new instance)
• clear apcu cache upon starting containers #2573
• enable compression for js files in Nextcloud #2576
• move permission overwrite to better place before innstallation #2577 (test on new instance)
• Bump docker from 23.0.6-cli to 24.0.2-cli in /Containers/mastercontainer #2619
• update to Nextcloud 26.0.2 #2602 (test with new instance)
• increase supported aio app versions #2603
• set newMajorVersion to empty string #2604 (test on new instance)
• update Nextcloud container to php 8.1 and alpine 3.17 #2605
• enable imaginary by default #2607 (test on new instance)
• remove imaginary version check #2608
• add notes app to default apps #2609 (test on new instance)
• rework getbackupvolumes and getallbackupvolumes to be a bit more easy… #2621

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-releases/all-in-one/actions/runs/5123556719
• 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! (until 6.6.)
• 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