publish new images after recent PRs are merged and tested

[szaimen]

Follow up to #5896

(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: update to php8.4 #5970
• run-exec-commands.sh. adjust message when waiting for container #5990
• also add ui-secret to pi-hole and vaultwarden #5998
• initial commit szaimen/aio-smbserver#2
• Allow to add & remove community containers via the aio interface with nc31 #5937
• borg: allow to exclude datadir and preview folder from backup via .noaiobackup file #6009
• FTS: allow to adjust the ES_JAVA_OPTS #6005
• create nc-aio-guide when all the above is done (personal reopo)

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)
• 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!
• 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