publish new images after recent PRs are merged and tested

[szaimen]

Follow up to #7173

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

Tested:

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

• aio-smbserver: now compatible with arm64 as well #7246 will be tested by community
• build(deps): bump collabora/code from 25.04.7.1.1 to 25.04.7.3.1 in /Containers/collabora #7230
• mastercontainer: refactor docker api version check #7234
• refactor backup-mode handling #7238
• nextcloud: allow to configure mysql root cert #7216 will be tested by community
• fix remaining psalm issues #7182
• aio-interface: add button to update the backup list #7186
• aio-interface: always offer a reset backup location button #7185 (fixed with adjust DeleteBorgBackupLocationVars to also delete the borg.config file #7244)
• add com.docker.compose.project: nextcloud-aio label to all containers #7190
• update aio-caddy to v4 and add option for proxy protocol #7191 (test what happens if talk is disabled and no apache_ip_binding is configured)
• add notifications community container #7194 (test notifications and scrutiny together and scuritny without notifications)
• update private ip-ranges #7201
• fulltextsearch: disable memory locking #7206

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?q=is%3Apr+is%3Aopen+helm+)
• increase the version number in https://github.com/nextcloud/all-in-one/blob/main/php/templates/containers.twig#L20
• 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)
• test if collabora opens
• Run E2E test and wait for it to finish. See https://github.com/nextcloud/all-in-one/actions/workflows/playwright.yml
• 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! (until 10.12.)
• 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
• unpin AIO mastercontainer fails to start after update (20251128_084214) due to Docker socket connection error on Synology #7223
• pin template for updating all existing instances to the next Nextcloud major version #6198
• Merge the automated YAML updates PR if there should be one (https://github.com/nextcloud/all-in-one/pulls?q=is%3Apr+is%3Aopen+yaml)
• 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