cephrgw: recreate cnpg backup buckets on ec placement (step 3) (#316)

Final step of the ec migration: the old buckets were purged in #315, so the operator will now create fresh ones on the ec placement target. Restores the nine Bucket CRs with placementTarget: ec and retainOnDelete: true (purge disabled again for safety).

- re-add the nine cnpg backup Bucket resources on ec, retainOnDelete: true

Reviewed-on: #316
Co-authored-by: Ben Vincent <ben@unkin.net>
Co-committed-by: Ben Vincent <ben@unkin.net>

apps/base/encapi/cnpg_backup.yaml

@@ -20,6 +20,24 @@ spec:
   # in-flight restore can still reach the archive.
   retainOnDelete: true
 ---
+apiVersion: ceph.unkin.net/v1alpha1
+kind: Bucket
+metadata:
+  name: cnpg-encapi
+  namespace: encapi
+spec:
+  placementTarget: ec
+  bucketName: cnpg-encapi
+  # The owner user has full control of its own bucket (read + write), which is
+  # all the backup/restore identity needs — no extra BucketAccess grant.
+  ownerRef: cnpg-encapi-backup
+  versioning: false
+  tags:
+    app: encapi
+    purpose: cnpg-backup
+  # Never drop the backups if the CR is removed; retire buckets by hand.
+  retainOnDelete: true
+---
 # Nightly base backup. Continuous WAL archiving is always-on via the Cluster's
 # spec.backup.barmanObjectStore; this schedules the periodic full backup that
 # WAL is layered on top of. Schedules are staggered across clusters so the 8