What type of PR is this?

/kind bug

What this PR does / why we need it:

This PR fixes a bug in the DaemonSet controller where the NumberMisscheduled status field does not get updated when node properties (labels or taints) change, leading to incorrect DaemonSet status reporting.

Problem:
The syncNodeUpdate function in the DaemonSet controller has insufficient trigger conditions that only handle pod creation and deletion scenarios:

// Before: Only handles create/delete scenarios
if (shouldRun && !scheduled) || (!shouldContinueRunning && scheduled) {
    dsc.enqueueDaemonSet(ds)
}

This misses the critical third scenario where pods are already scheduled but their scheduling legitimacy changes due to node updates (e.g., when taints are added/removed).

Specific scenario that fails:

1. A DaemonSet pod gets scheduled on a node before the node is tainted as "not-ready"
2. When the node becomes ready and the taint is removed, the pod transitions from "misscheduled" to "correctly scheduled"
3. However, the DaemonSet status is not updated because the current logic doesn't trigger a sync for this state transition
4. The pod remains incorrectly flagged as misscheduled in the DaemonSet status

Solution:
Expand the trigger conditions to ensure any DaemonSet that has a relationship with the updated node (either should run on it or already has pods on it) gets resynced:

// After: Handles all scenarios including state transitions
if shouldRun || scheduled {
    dsc.enqueueDaemonSet(ds)
}

This ensures that DaemonSet status fields like NumberMisscheduled, CurrentNumberScheduled, etc., are recalculated whenever node properties change.

Which issue(s) this PR is related to:

Fixes #132459

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: