publish new images after recent PRs are merged and tested

[szaimen]

Follow up to #460

tested:

• Dependency updates #479 (does it work overall?)
• add a beta channel #487 (does the link work?)
• improve update handling when changing channels #478
• Bump collabora/code from 21.11.3.4.1 to 21.11.3.6.1 in /Containers/collabora #468

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 final test using the develop channel
• 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
• wait a week and see if new bugs get reported (till ~20.04.) (maybe this should go in for 1.0.0 stalbe? a0cef69 refactor detection of available container updates #497)
• if not, publish to latest:
• 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
• create a new milestone that is called next
• move all open issues/PRs to that new milestone
• close the old milestone