publish new images after recent PRs are merged and tested

[szaimen]

Follow up to #2816

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

Tested:

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

• show AIO password #2787 (doesnt work currrently, says that the function was not found; fixed with ea46ed4?)
• add note to AIO interface that imaginary is incompatible with SSE #2815
• remove r3 from coturn version #2817
• small improvement to files_antivirus settings #2842
• Remove warning about Docker Desktop v4.19 #2930
• apache - expose udp for http3 to work #2828
• mastercontainer - disable http3 #2826
• add low-on-space notification #2858
• add logging in case disk space is low and thus login might fail #2857
• revert adjustment of tempdirectory #2868
• coturn - pin alpine version correctly #2922
• rework notify-push in order to export values as env #2869
• make domaincheck container read-only #2870 (test with new install)
• make postgresql container read-only #2871 (also test with new install and adjust timezone)
• make apache container read-only #2874 (fixed with 71481cd)
• make talk container read-only #2875 (test if going into call works, test with mobile and also admin checks)
• make talk-recording read-only #2876 (test if recording works)
• Bump collabora/code from 23.05.0.5.1 to 23.05.1.2.1 in /Containers/collabora #2884
• imaginary - add tmpfs in /tmp #2926

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 (done with https://github.com/nextcloud-releases/all-in-one/actions/runs/5551586702)
• 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! (till 20.7.)
• 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