Pull bind CRDs from operator repo instead of vendoring

References the CRD bundle from the bind-operator repo by a stable raw URL
so the CRDs never drift from the operator, matching how other apps import
upstream manifests.

- replace the nine vendored crds/*.yaml with a single remote resource:
  git.unkin.net/unkin/bind-operator raw config/crd/install.yaml at v0.1.1
- bump the operator image to v0.1.1 so the running operator and its CRDs
  come from the same tag

apps/base/bind-system/kustomization.yaml

@@ -4,14 +4,8 @@ kind: Kustomization
 
 resources:
   - namespace.yaml
-  - crds/bind.unkin.net_bindclusters.yaml
-  - crds/bind.unkin.net_bindzones.yaml
-  - crds/bind.unkin.net_bindviews.yaml
-  - crds/bind.unkin.net_bindtsigkeys.yaml
-  - crds/bind.unkin.net_bindacls.yaml
-  - crds/bind.unkin.net_bindcatalogzones.yaml
-  - crds/bind.unkin.net_bindpolicies.yaml
-  - crds/bind.unkin.net_binddnssecpolicies.yaml
-  - crds/bind.unkin.net_dnsrecords.yaml
+  # CRDs are pulled from the bind-operator repo at the matching tag rather than
+  # vendored here, so they never drift from the operator.
+  - https://git.unkin.net/unkin/bind-operator/raw/tag/v0.1.1/config/crd/install.yaml
   - rbac.yaml
   - deployment.yaml