fix: Separate Backup CRs into their own kustomization

The Backup and Restore CRs need the rancher-backup CRDs to exist first.
Moved them to a separate kustomization that depends on the operator being ready.

infrastructure/addons/rancher-backup/backup-recurring.yaml

@@ -1,17 +0,0 @@
-apiVersion: resources.cattle.io/v1
-kind: Backup
-metadata:
-  name: rancher-b2-recurring
-  namespace: cattle-resources-system
-spec:
-  resourceSetName: rancher-resource-set-full
-  storageLocation:
-    s3:
-      credentialSecretName: rancher-b2-creds
-      credentialSecretNamespace: cattle-resources-system
-      bucketName: HetznerTerra
-      folder: rancher-backups
-      endpoint: s3.us-east-005.backblazeb2.com
-      region: us-east-005
-  schedule: "0 3 * * *"
-  retentionCount: 7

infrastructure/addons/rancher-backup/kustomization.yaml

@@ -5,5 +5,3 @@ resources:
   - helmrepository-rancher-backup.yaml
   - helmrelease-rancher-backup.yaml
   - b2-credentials-externalsecret.yaml
-  - backup-recurring.yaml
-  - restore-from-b2.yaml

infrastructure/addons/rancher-backup/restore-from-b2.yaml

@@ -1,19 +0,0 @@
-# Uncomment and set backupFilename to restore from a specific backup on rebuild.
-# Find the latest backup filename in B2: rancher-backups/ folder.
-# After restore succeeds, Rancher will have all users/settings from the backup.
-#
-# apiVersion: resources.cattle.io/v1
-# kind: Restore
-# metadata:
-#   name: restore-from-b2
-#   namespace: cattle-resources-system
-# spec:
-#   backupFilename: <backup-filename-from-b2>
-#   storageLocation:
-#     s3:
-#       credentialSecretName: rancher-b2-creds
-#       credentialSecretNamespace: cattle-resources-system
-#       bucketName: HetznerTerra
-#       folder: rancher-backups
-#       endpoint: s3.us-east-005.backblazeb2.com
-#       region: us-east-005