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

```

Inizia leggendo BackupServiceImplementation e la gestione dei CRD Backup e BackupSchedule descritta nell’issue. Traccia come viene selezionato barmanObjectKey rispetto ai parametri di pluginConfiguration, quindi individua i test Backup esistenti e verifica che un barmanObjectName configurato esplicitamente sovrascriva l’object store del cluster sia per le risorse Backup sia per le risorse BackupSchedule.

Scritto dal modello di indicizzazione a partire dal testo della issue.