Inconsistent Dry-Run Behavior Between Controllers

Dry-run behavior differs between RuleController and NodeController

Current Behavior

• RuleController evaluates dry-run rules and reports what would happen(here: https://github.com/kubernetes-sigs/node-readiness-controller/blob/main/internal/controller/nodereadinessrule_controller.go#L544).
• NodeController skips dry-run rules entirely, producing no output when nodes change(here: https://github.com/kubernetes-sigs/node-readiness-controller/blob/main/internal/controller/node_controller.go#L88).

Problem
When node labels or conditions change, we will get no visibility into whether rules would match or what taint operations would occur.

Question: is that by design? If no we should evaluate in nodeController too when we do dryRun=True and update the nodeStatus maybe(here: https://github.com/kubernetes-sigs/node-readiness-controller/blob/main/internal/controller/nodereadinessrule_controller.go#L350)

Start by comparing the dry-run paths at internal/controller/nodereadinessrule_controller.go:544 and :350 with internal/controller/node_controller.go:88. Trace how node changes reach NodeController and how nodeStatus is updated, then use the comment discussion to determine whether skipping dry-run rules is intentional. Done means the intended behavior is documented and both controller paths provide consistent dry-run visibility.