publish new images after recent PRs are merged and tested

[szaimen]

Follow up to #7393

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

Tested:

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

• mastercontainer: make check for correct volume name more strict #7485 (test this also with docker compoese)
• only allow to set APACHE_ADDITIONAL_NETWORK via environmental variable and do not restore it on backup restore #7520 (will be tested by community)
• aio-interface: rename Collabora everywhere to Nextcloud Office #7516 (fixed with a037be9)
• nextcloud-entrypoint.sh: improve GPG key import method #7502 (will be tested by community)
• Lower case method names in ConfigurationManager #7501 (will be tested by community)
• Fix: Additional Collabora options not working correctly #7481
• deprecate nocodb community container #7477
• Adjust local-ai community container to add Vulkan support #5797 (will be tested by community)
• Nextcloud dependency update #7442
• Use property hooks to replace classic getter and setter methods. #7392
• refactor: change private properties to public in Container class #7406
• feat: Add office switcher with feature comparison #7421
• move version to a dedicated file #7436
• insert the AIO version into Nextcloud's system config #7437
• nextcloud-entrypoint: make recording server dependent on REMOVE_DISABLED_APPS #7454 (will be tested by community)
• add wud.watch=false to all containers #7455 (improved with a7c091a)
• DockeractionManager: rewrite PullImage function to re-try 3 times before failing #7457
• postgres.config.php: fix PDO::MYSQL_ATTR_SSL_CA #7462
• CreateContainer: also insert the max shutdown time into the container itself #7468

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/includes/aio-version.twig
• 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-on-workflow-dispatch.yml https://github.com/nextcloud/all-in-one/actions/runs/21511213907
• 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 two weeks and see if new bugs get reported and don't merge any PR into the main branch of this repo in the meantime! (until 11.2.)
• 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?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