[Improvement]: Add update monitoring (and possibility for auto upgrades) of services and all containers

[peaklabs-dev]

Description

Currently, we can manually add a tag to all of our resources and then manually re-deploy all of the resources using the tag. This is not an ideal workflow for keeping containers up to date.

Minimal Reproduction (if possible, example repository)

Idea of an ideal update workflow (only with coolify), as this workflow currently requires the watchtower docker container:

• [ ] 1. Coolify let us set an interval (via cron) in this set interval coolify will re-pull all images of all containers and if there are updates it will show us an icon in coolify that the container needs to be updated (re-deployed). Do not pull all images at once but 2 at a time for performance reasons --> Update available --> Automatically check for updates for docker images (on the docker hub and services), then if there is an update it will show a badge Update available.
• [ ] It would also be good if we could get a notification via the notification settings we have set in coolify as soon as there are containers that have an update.
• [ ] 2. We can go to a centralized interface and hit update all, which will re-deploy all containers that have a new image ready -> so multiple updates. (better than adding update tag to all containers and going to the tag area)
• [ ] Manual and automated rollback: A rollback feature for normal docker containers and services (other than git) would be amazing, so that when the health check or deployment fails for the new image for the container, the container automatically goes back to the old state it had before (using the old image to deploy the one that was available before, maybe to old image is stored in localhost as long as the container is not healty). Example I can depoly the new container for ghost and if the minor PHP update breaks something I can go back to the old image stored in localhost (I hit rollback manully) or if health check fails it rolls back automatically --> Better Image management goes alongside this see: https://github.com/coollabsio/coolify/issues/2499
• [ ] 3. Not as necessary as most likely disabled in production: a switch to automatically update all containers so once a new image is found automatically update
• [ ] Update notifications for coolify panel updates
• [ ] Update notifications for docker image updates

Exception or Error

No response

Version