publish new images after recent PRs are merged and tested

[szaimen]

Follow up to #1571

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

Tested:

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

• rename values of containers definition to match docker-compose values #1595
• allow to hide containers from the interface via display_name #1598
• allow to make wrong database intialization better debuggable #1621
• borg - add progress back and add some additional output #1622 (fixed with 1605431)
• add types for missing ones and bring psalm-baseline down to zero #1645
• improve healthcheck to only exit 1 if it is started #1615 (fixed with fix healthcheck for nextcloud and database #1657)
• change dockerfile links, add tzdata to fulltext, migrate healthchecks to nc #1619
• update mastercontainer to php 8.1 #1587
• improve containeers schema #1604
• allow to add container to host network #1597 (test this e.g. with borg container; fixed with fix adding containers to the host network #1655)
• refactor containerports #1635 (fixed with fix exposing containers #1656)
• rename volume name to source and volume location to destination #1637
• allow to enable shipped apps during startup #1654
• secrets should only get generated if defined in secrets of container.… #1596 (should be tested with a new instance)
• allow to add the /dev/dri device into the container and refactor devices #1659 (test with borg and in a VM)
• set remote_font_config for collabora #1663
• add twofactor_totp back as default enabled app #1658 (does not need to be tested)
• allow to repair the integrity of the backup archive #1670 (fixed with d8f24b8)
• add ulimit for the talk container due to a bug in libwebsockets #1671

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! (until 12.01.)
• 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
• change the pre-release to be a stable and the latest release and remove Beta from the title
• close the old milestone