feat: eventually consistent NVOS password rotation support

[jayzhudev]

Is this a new feature, an enhancement, or a change to existing functionality?

New Feature

How would you describe the priority of this feature request

Medium

Please provide a clear description of problem this feature solves

Add backend-agnostic, eventually consistent NVOS password rotation through component-manager. Securely manage versioned credentials, track per-switch convergence, reconcile uncertain outcomes, and recover after restarts without blind retries or exposing password material.

Feature Description

• System shall rotate NVOS credentials through component-manager, independent of backend implementation.
• System shall manage versioned credentials in the authoritative credential store.
• System shall track durable per-switch rotation and convergence state.
• System shall support asynchronous submission and job observation.
• System shall reconcile uncertain outcomes before retrying or promoting credentials.
• System shall recover safely after restarts without blind retries.
• System shall not expose password material through persistence, logs, metrics, or errors.

Describe your ideal solution

No response

Describe any alternatives you have considered

No response

Additional context

This feature request is related to #2041

Code of Conduct

• I agree to follow NVIDIA Infra Controller's Code of Conduct
• I have searched the open feature requests and have found no duplicates for this feature request