Factor HelmRelease defaults and drift detection into k8s/bases/components/ like the platform

[devantler]

🤖 Generated by the Daily AI Engineer

Problem. The reference platform DRYs its HelmRelease configuration through reusable Kustomize components (k8s/bases/components/helmrelease-flux-defaults, helmrelease-drift-detection); the template has no components/ directory, so every scaffolded HelmRelease repeats those settings and misses drift detection defaults.

Proposed direction. Port the two components (genericized), wire them into the template's HelmRelease-bearing bases, and note the pattern in the template docs. Also sweep the remaining vendored/raw-manifest infra for HelmRelease candidates now that theme 3's CoreDNS migration (#14 via #62) has landed.

Rough size. M

Part of #24

[coderabbitai]

🔗 Related PRs

#62 - feat(coredns): migrate docker-provider CoreDNS from Deployment to HelmRelease [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!