Backup path change prepends app name and breaks user-defined prefix structure

To Reproduce

1. Configure a backup with a custom prefix (e.g. {server-name}/web-server)
2. Run a backup
3. Inspect the object path in the bucket

Current vs. Expected behavior

Current Behavior

Backups are stored as:

bucket/{app name}/{prefix defined in backup settings}/{object name}

Expected Behavior

Backups should be stored as:

bucket/{prefix}/{object name}

The prefix should fully define the object path without additional automatic segments.

Provide environment information

Dokploy Version: v0.28.6
S3 Backup location: AWS S3

Which area(s) are affected? (Select all that apply)

Docker, Application

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

Impact / Additional Context

Previously, users could define flexible and meaningful structures:

• Dokploy backups:

  bucket/{server-name}/web-server/{object name}
  

• Docker volume backups:

  bucket/{server-name}/docker/{app name}/{service name}/{object name}
  

With the new behavior, this becomes:

bucket/{app name}/{server-name}/web-server/{object name}

This:

• Breaks existing backup organization
• Makes the configured "prefix" no longer function as a true prefix
• Reduces flexibility for structuring backups across systems

Will you send a PR to fix it?

Yes

Start by tracing the S3 backup path construction from the backup settings and reproduce the custom-prefix case described here. The work is done when the configured prefix directly precedes the object name, without an automatically added application-name segment, while existing Docker volume backup structure remains correct.