Implement retry logic in WS-Man messages (configurable, non-permanent failures only)

[sudhir-intc]

Is your feature request related to a problem? Please describe.
Currently, the WS-Man message handling does not implement retry logic. Unexpected and intermittent errors (such as parse failures) can cause these message calls to fail immediately, reducing system robustness. There is no mechanism to allow automatic retries for recoverable errors.

Describe the solution you'd like
Add configurable retry logic to WS-Man message handling:

• Max attempts should default to 3, but be configurable per call.
• Retries are to be performed only for unexpected scenarios (example: XML or response parse failures, timeouts, or similar transient conditions).
• Failures due to authentication errors, configuration issues, or other permanent errors should not be retried—they must fail immediately on first occurrence.

Describe alternatives you've considered

• Only applying retry logic globally (but per-call configurability is preferred).
• Letting errors always propagate without any retry attempts (current state).

Additional context

• Please specify any additional error scenarios to include/exclude from retry, or provide example stack traces if available.
• Let us know if you have specific retry libraries or patterns you want considered or avoided.

[sudhir-intc]

@madhavilosetty-intel : Could you please review this issue and help improve the content if there's some additional handling to be done.