publish new images after recent PRs are merged and tested

[szaimen]

Follow up to #2610

(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 disable/enable talk-recording #2674
• add talk-recording container #2645
• Move vars to lets and fix some things with recording.conf #2679
• janus - enable full-trickle support #2672
• add note about SELinux and Docker Desktop #2670
• Dockerfiles - Add USER to all files #2661 (fixed with ad570de)
• Make sure to disable apps that could not get enabled after an update #2660
• remove the updatenotification app also if already updating to next ma… #2658
• try to speed up initial login by not removing the bridge network from… #2664
• Remove collaboras font volume as it does not seem to be used #2653
• Switch from mawk to built-in awk #2639
• allow to specify read_only root FS in containers definition #2641
• redis - enable readonlyrootfs #2642
• allow to install 27 on new install #2685 (test with new install)

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 (and check if add talk recording to build and promote workflows nextcloud-releases/all-in-one#40 works)
• 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 (and check if add talk recording to build and promote workflows nextcloud-releases/all-in-one#40 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) 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 13.06.)
• 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 (and check if add talk recording to build and promote workflows nextcloud-releases/all-in-one#40 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