Backup to different object store

Hi,
first of all thank you for the amazing work!

I might have a bit of an odd use case:
Currently I have two S3 compatible object stores. One onsite and one for offsite backups. Because the connection to the offsite one can be quite slow (this is a homelab setup), I didn't want to send WALs to the offsite S3 but just baseline backups every so often.

From what I can tell the BackupServiceImplementation currently just uses the barmanObjectKey from the cluster definition and ignores any parameters specified directly on the Backup or BackupSchedule CRD.

Would it be possible to support overriding the object store in the backup crd like this?

```
apiVersion: postgresql.cnpg.io/v1
kind: Backup
metadata:
name: backup-example
spec:
cluster:
name: pg-nextcloud
method: plugin
pluginConfiguration:
name: barman-cloud.cloudnative-pg.io
parameters:
barmanObjectName: anotherObjectStore

```

Comienza leyendo BackupServiceImplementation y el manejo de los CRD Backup y BackupSchedule descrito en la issue. Sigue cómo se selecciona barmanObjectKey frente a los parámetros de pluginConfiguration; después, identifica las pruebas de Backup existentes y verifica que un barmanObjectName configurado explícitamente sobrescribe el almacén de objetos del clúster tanto para los recursos Backup como para los recursos BackupSchedule.

Escrito por el modelo de indexación a partir del texto del issue.