fix(coredns): revert template plugin — broke cluster DNS

Restores the original Corefile without the *.renner.uno template
synthesis. ConfigMap stays Flux-managed so CoreDNS has a valid
config to reload; reverting the whole kustomization would have
deleted the ConfigMap via Flux prune, leaving CoreDNS with no
Corefile at all.

kube-dns-lb Service and the coredns-config kustomization directory
are intentionally left in place — they're harmless in isolation
and useful if we later reintroduce a corrected template.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

kubernetes/infrastructure/coredns-config/configmap.yaml

@@ -16,13 +16,6 @@ data:
         }
         prometheus :9153
 
-        template IN A renner.uno {
-            answer "{{ .Name }} 60 IN A 10.2.40.80"
-        }
-        template IN AAAA renner.uno {
-            answer "{{ .Name }} 60 IN AAAA fd40::80"
-        }
-
         kubernetes cluster.local in-addr.arpa ip6.arpa {
             pods insecure
             fallthrough in-addr.arpa ip6.arpa