publish new images after recent PRs are merged and tested

[szaimen]

Follow up to #1041

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

Tested:

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

• improve healthcheck for mastercontainer #1116

Tasks to do for new release:

• 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
• 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) 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! (til 12.09.)
• 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
• merge Yaml updates #1045
• 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
• change the pre-release to be a stable release and remove Beta from the title
• close the old milestone