Bump cephrgw-operator CRDs to v0.3.0

The cephrgw-system kustomization pinned the CRD source to tag v0.1.0, so the
in-cluster CRDs never gained the fields added since: v0.2.0's fine-grained
BucketAccess policy fields and v0.3.0's adoption fields (retainOnDelete,
managePolicy, status.adopted). The running operator is v0.3.0, so applying
those specs fails strict decoding. Move the CRD tag in step with the image.

- point the CRD install.yaml at raw/tag/v0.3.0

Claude-Session: https://claude.ai/code/session_016CEncETbf8cvy1PhsHfFHM

apps/base/cephrgw-system/kustomization.yaml

@@ -6,7 +6,7 @@ resources:
   - namespace.yaml
   # CRDs are pulled from the cephrgw-operator repo at the matching tag rather
   # than vendored here, so they never drift from the operator.
-  - https://git.unkin.net/unkin/cephrgw-operator/raw/tag/v0.1.0/config/crd/install.yaml
+  - https://git.unkin.net/unkin/cephrgw-operator/raw/tag/v0.3.0/config/crd/install.yaml
   - rbac.yaml
   - deployment.yaml
   - vaultauth.yaml