[Release-1.29] - rke2-coredns: don't hardcode force_tcp in node-local-dns configmap

[thomasferrandiz]

Backport fix for rke2-coredns: don't hardcode force_tcp in node-local-dns configmap

• rke2-coredns: don't hardcode force_tcp in node-local-dns configmap #7265

[mdrahman-suse]

Validated on release-1.29 branch with commit 0a3c4f4

Testing

Followed steps mentioned here: #7266 (comment)

Validation

$ rke2 -v
rke2 version v1.29.10+dev.0a3c4f4a (0a3c4f4ac6b7e6a9a48efc7da0428b98a0cb7499)
go version go1.22.8 X:boringcrypto

$ sudo cat /var/lib/rancher/rke2/data/v1.29.10-dev.0a3c4f4a-472803fd5630/charts/rke2-coredns.yaml | grep "rke2-coredns"
  name: "rke2-coredns"
    helm.cattle.io/chart-url: "https://rke2-charts.rancher.io/assets/rke2-coredns/rke2-coredns-1.33.005.tgz"

• After deploying rke2 with nodelocaldns activated

## Configmap got created
$ kubectl get configmaps -n kube-system node-local-dns
NAME             DATA   AGE
node-local-dns   1      3m50s

## Configmap has the expected block
$ kubectl describe configmaps -n kube-system node-local-dns
Name:         node-local-dns
Namespace:    kube-system
...
.:53 {
    errors
    cache 30
    reload
    loop
    bind 169.254.20.10 10.43.0.10
    forward . __PILLAR__UPSTREAM__SERVERS__
    prometheus :9253
    }