publish new images after recent PRs are merged and tested

[szaimen]

Follow up to #216

tested:

• Do not disconnect containers from network #246
• enforce startup order #253
• allow nextcloud to access outside directories #254
• move trusted_proxies to entrypoint #266
• ip-addresses are not supported as domain #268

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-collabora
  • aio-nextcloud
  • aio-postgresql
• 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