Regenerate helm golden files for the forwarder's dnsPolicy

The forwarder Deployment now renders dnsPolicy: ClusterFirst explicitly,
which is the Kubernetes default it already had implicitly.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QNTDU7nLkCv8qSJHW3kTE9
Signed-off-by: arik <alon.arik@gmail.com>

Author: arikalon1

tests/helm_golden/default.yaml

@@ -707,6 +707,7 @@ spec:
     spec:
       serviceAccountName: robusta-forwarder-service-account
       automountServiceAccountToken: true
+      dnsPolicy: ClusterFirst
       containers:
       - name: kubewatch
         # this is a custom version of kubewatch built from https://github.com/aantn/kubewatch

tests/helm_golden/holmes.yaml

@@ -1256,6 +1256,7 @@ spec:
     spec:
       serviceAccountName: robusta-forwarder-service-account
       automountServiceAccountToken: true
+      dnsPolicy: ClusterFirst
       containers:
       - name: kubewatch
         # this is a custom version of kubewatch built from https://github.com/aantn/kubewatch

tests/helm_golden/openshift.yaml

@@ -1322,6 +1322,7 @@ spec:
     spec:
       serviceAccountName: robusta-forwarder-service-account
       automountServiceAccountToken: true
+      dnsPolicy: ClusterFirst
       containers:
       - name: kubewatch
         # this is a custom version of kubewatch built from https://github.com/aantn/kubewatch