Fix circular dependency with Hetzner CCM Helm deployment and Cilium CNI

Fixes #1879

When using Hetzner CCM via Helm with Cilium CNI, the Cilium operator pods
couldn't schedule due to a circular dependency:
- CCM pods needed CNI network to start (without hostNetwork)
- Cilium needed CCM to initialize nodes first

This fix adds `hostNetwork: true` to the Hetzner CCM Helm values,
aligning the Helm deployment behavior with the working customization
method. This allows CCM to start using host networking before CNI is
ready, breaking the circular dependency.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

Author: mysticaltech

locals.tf

@@ -593,6 +593,7 @@ hubble:
 %{endfor~}
 %{endif~}
 
+
 MTU: 1450
   EOT
 
@@ -701,6 +702,8 @@ env:
     value: "${!local.using_klipper_lb}"
   HCLOUD_LOAD_BALANCERS_DISABLE_PRIVATE_INGRESS:
     value: "true"
+# Use host network to avoid circular dependency with CNI
+hostNetwork: true
   EOT
 
   haproxy_values = var.haproxy_values != "" ? var.haproxy_values : <<EOT