publish new images after recent PRs are merged and tested

[szaimen]

Follow up to #4575

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

Tested:

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

• Nextcloud dependency update #4710
• wait for talk-recording-server update? not for now
• nextcloud: wait for redis to start #4728
• Update stalwart.json - add port definition for web admin interface #4556
• Revert "Revert "apache - drop SetEnv proxy-sendcl 1"" #4713
• Bump strukturag/nextcloud-spreed-signaling from 1.3.0 to 1.3.1 in /Containers/talk #4712
• AIO interface: document limitation regarding restoring of community container data #4707
• apache: remove caddy-imports #4706
• AIO interface: add note how to reset the AIO instance #4709
• change the rewrite for remote.php #4651 (check admin overview on existing install)
• fix bug with getting api_version #4692
• add borg_backup_mode to Backup container status #4693 (test restore)
• Add a config option for the postgres database port #4433 (test existing and new install)
• fix limiting php-fpm socket to certain ip-addresses #4685
• Bump strukturag/nextcloud-spreed-signaling from 1.2.4 to 1.3.0 in /Containers/talk #4687
• improve UX and UI #4588 (test per commit)
  • adjust link color
  • change Nextcloud AIO setup to All-in-One setup
  • add warning toe note down the password and make it big fixed with 8fd457f
  • change password to passphrase
  • adjust loader color to match nextcloud blue
  • pre-fill the timezone
  • try to fix glitchy buttons
  • add instructions how to inspect container logs fixed with 8fd457f
  • change wording
  • adjust wording
  • rename password to encryption password

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 https://github.com/nextcloud-releases/all-in-one/actions/runs/9301603870
• 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; also document this time that beta testers should test if talk calls still work for them) 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 one 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 (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)
• remove changelog entry regarding beta testers
• close the old milestone