fix(agent): skip unchanged restored condition writes

[hutm]

Problem

Repeated restore reconciliations apply the same nvidia.com/Restored condition even when its status, reason, and message have not changed. Each no-op write creates a new Pod resource version and triggers another informer event.

Why

Restore dependencies can remain pending across several reconciliations. Avoiding identical status writes reduces API server traffic and self-induced reconciliation, especially when many restores run concurrently.

Change

Skip the status apply when the existing condition already matches. Real transitions continue through server-side apply and retain the existing LastTransitionTime behavior.

Testing

• Added coverage for skipping an identical condition and persisting a changed condition.
• Ran the complete agent test suite.

Fixes #353

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

_{Comment @coderabbitai help to get the list of available commands.}