fix:return evaluation errors from processAllNodesForRule

[dorodb-web22]

Description

processAllNodesForRule was catching errors from evaluateRuleForNode but always returning nil. This prevented RuleReconciler.Reconcile from seeing any failures, so controller-runtime never triggered a requeue on transient errors like API conflicts or patch failures.

This fix accumulates errors across the node loop and returns them via errors.Join, using the same pattern applied to processNodeAgainstAllRules in #222. The existing behavior of continuing evaluation across all nodes is preserved.

Related Issue

Fixes #234

Type of Change

/kind bug

Testing

make test
make lint

Checklist

• make test passes
• make lint passes

Does this PR introduce a user-facing change?

NONE

[netlify]

✅ Deploy Preview for node-readiness-controller canceled.

Name	Link
🔨 Latest commit	249bdf5
🔍 Latest deploy log	https://app.netlify.com/projects/node-readiness-controller/deploys/6a00c4ea2824790008f30d2e

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dorodb-web22
Once this PR has been reviewed and has the lgtm label, please assign mrunalp for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @dorodb-web22. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.