feat(chart): add DaemonSet support via kind value

[vikzhex]

Add configurable workload kind (Deployment or DaemonSet) to the Helm chart.
When kind is set to DaemonSet, the chart uses updateStrategy instead of
strategy and omits replicas, as required by the DaemonSet spec.

Motivation

In our environment we need to monitor network connectivity (latency, packet loss)
from every worker node independently. A single Deployment replica only tests
connectivity from one node, making it impossible to detect per-node network
issues such as faulty NICs, misconfigured routes, or degraded uplinks.

Using a Deployment with podAntiAffinity to spread across nodes requires
manually tracking the replica count to match the number of target nodes —
any node scaling event (adding/removing nodes) would require updating
replicaCount, which is error-prone and hard to automate.

A DaemonSet solves both problems: it automatically places one instance on
each matching node (via nodeSelector or nodeAffinity) and adjusts to node
scaling without manual intervention.

Changes

• Added kind value (Deployment by default) to switch between Deployment
  and DaemonSet
• When kind: DaemonSet: uses updateStrategy instead of strategy,
  omits replicas
• Fully backward compatible — no changes to existing behavior when kind
  is not set

Usage

kind: DaemonSet

strategy:
  type: RollingUpdate
  rollingUpdate:
    maxUnavailable: 20%