publish new images after recent PRs are merged and tested

[szaimen]

Follow up to #270

tested:

• customize collabora a bit #252
• migrate borgbackup to alpine #306 (see if backups still can get created, restored...) reverted because of missing llfuse in main repo.
• show the current channel and add links to the changelogs #307
• don't update database container if it failed before #313
• Dependency updates #311 (check if mastercontainer still works)
• correctly delete sessions older than 24h #325
• allow to change the location of Nextclouds datadir #326
• check if the startup command was executed successfully #328
• allow to change the password #329
• add optional section #330
• improve domain check #331

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-talk
• 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