Backups failing with new cluster/objectstorage

<!--
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Bug" label.

Issue tracker:

- https://gitlab.com/ongresinc/stackgres/-/issues?label_name=Bug

and verify the issue you're about to submit isn't a duplicate.
-->
### Summary

<!--(Summarize the bug encountered concisely)-->
After upgrading to StackGres 1.3.0, I backed up and recreated my cluster because of other issues I encountered. Along with this, I created a new Object Storage configuration. This appears to be due to the backup job expecting a SGBackupConfig to exist when none does as I created this object storage config after upgrading to 1.3.0

### Current Behaviour 

Backup is stuck in pending

#### Steps to reproduce

1. Create a new ObjectStorage
2. Create a new cluster utilizing the new ObjectStorage
3. Create a new backup

### Expected Behaviour

Backup is successful

### Possible Solution

<!-- What do you think is the possible solution for the bug -->

Update items still looking for legacy SGBackupConfig

### Environment

- StackGres version: 1.3.0
<!-- if you have used helm, you can use:  `helm get notes -n stackgres stackgres-operator` 
more generic: `kubectl get deployments -n stackgres stackgres-operator --template '{{ printf "%s\n" (index .spec.template.spec.containers 0).image }}'`
-->
- Kubernetes version:
Client Version: v1.25.0
Kustomize Version: v4.5.7
Server Version: v1.24.4+k3s1
- Cloud provider or hardware configuration:
Assorted x86 bare metal and VMs

### Relevant logs and/or screenshots

```
➜  ~ kubectl describe sgbackup bk2022-09-03-15-1-7
Name:         bk2022-09-03-15-1-7
Namespace:    default
Labels:       <none>
Annotations:  stackgres.io/operatorVersion: 1.3.0
API Version:  stackgres.io/v1
Kind:         SGBackup
Metadata:
  Creation Timestamp:  2022-09-03T15:01:12Z
  Generation:          2
  Managed Fields:
    API Version:  stackgres.io/v1
    Fields Type:  FieldsV1
    fieldsV1:
      f:spec:
        .:
        f:managedLifecycle:
        f:sgCluster:
      f:status:
        .:
        f:process:
          .:
          f:status:
    Manager:         okhttp
    Operation:       Update
    Time:            2022-09-03T15:01:17Z
  Resource Version:  203653145
  UID:               e5dbe4ad-0a2a-468f-9163-d80d2cd7b336
Spec:
  Managed Lifecycle:  true
  Sg Cluster:         postgresql
Status:
  Process:
    Status:  Pending
Events:
  Type     Reason              Age                  From                Message
  ----     ------              ----                 ----                -------
  Normal   BackupCreated       3m21s                stackgres-operator  Backup default.bk2022-09-03-15-1-7 created: +Job:bk2022-09-03-15-1-7-backup
  Warning  BackupConfigFailed  1s (x21 over 3m21s)  stackgres-operator  Missing SGBackupConfig for cluster default.postgresql
  Normal   BackupUpdated       1s (x20 over 3m11s)  stackgres-operator  Backup default.bk2022-09-03-15-1-7 updated: Job:bk2022-09-03-15-1-7-backup (+/spec/completionMode -> NonIndexed), Job:bk2022-09-03-15-1-7-backup (+/spec/suspend -> false)
```

```➜  ~ kubectl logs -f bk2022-09-03-15-1-7-backup-mbp7m
Lock acquired
Updating backup CR
/usr/local/bin/create-backup.sh: line 287:  2666 Killed                  kubectl get "$BACKUP_CRD_NAME" -n "$CLUSTER_NAMESPACE" "$BACKUP_NAME" -o yaml
error: must specify --patch or --patch-file containing the contents of the patch
Lock released
cat: /tmp/backup-push: No such file or directory
Backup failed
```

Story points: 2.0