feat: Allow multiple backup schedules or multiple destinations per resource

What problem will this feature address?

Currently, Dokploy restricts each database or application to a single backup configuration. Once a backup job is created, the UI hides the option to add another one.

This makes it difficult to implement a robust 3-2-1 backup strategy natively. For example, a user cannot configure Dokploy to back up a Postgres database to a local on-premise NAS and simultaneously send a copy to an off-site remote server or public cloud destination.

Describe the solution you'd like

I would like the ability to create multiple independent backup jobs for a single resource.

Ideally, the "Create Backup" button should remain available even if a backup job already exists. This would allow users to define separate cron expressions, retention policies, and destinations (e.g., Job 1 goes to Local S3 hourly; Job 2 goes to Remote S3 daily). Alternatively, a single backup job could allow the selection of multiple configured destinations.

Describe alternatives you've considered

Storage-side replication: Using external tools like rclone, Synology Cloud Sync, or custom cron scripts on the primary backup target to mirror the data to a secondary location. While this works, it introduces external failure points, adds infrastructure complexity, and prevents Dokploy from centralizing backup logs and status alerts.

Additional context

No response

Will you send a PR to implement it?

No

The payload names no files or tests. Start by tracing the existing backup configuration and the Create Backup UI, then inspect how schedules, retention policies, destinations, logs, and alerts are handled. Done means one resource can support independent backup jobs or multiple destinations without hiding the Create Backup option.