publish new images after recent PRs are merged and tested

[szaimen]

Follow up to #302

tested:

• correctly disable database update if it failed before #335
• allow to get the mastercontainer logs from the frontend #336
• refactor some config logic #348
• move inline javascript to its own file #347
• fix domaincheck startup #352
• allow to check for restarting state #372
• Disallow creation of local external storage in some cases #368 (only testable with 23.0.3 and above)
• get caddy and apcu correctly #369
• improve error logging in dockeractionmanager #339
• allow to upgrade the mastercontainer even if no update was found #370
• list newest backups first #375
• move the mastercontainer section #377 (does the added link work?)
• add clamav as option #378

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
• deploy from develop to latest. See https://github.com/nextcloud/all-in-one/blob/main/develop.md#how-to-promote-builds-from-develop-to-latest
  • all-in-one
  • aio-apache
  • aio-nextcloud
  • aio-clamav
  • other?
• tag a new release here on github which fits the version number (and use vX.Y.Z as tag and title, use the autogenerated changelog)
• 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
• close the old milestone