Add fallback for rollout restart when annotations are missing (HTTP 422)

[dkaukov]

Description

This PR adds a fallback for rollout restart when patching fails with HTTP 422 (Unprocessable Entity).
If adding the kubectl.kubernetes.io/restartedAt annotation fails (e.g., because the annotations field doesn't exist), we retry the patch with one that creates the annotations map.

Fixes: #7072

---

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change
• Chore (non-breaking change which doesn't affect codebase;
  test, version modification, documentation, etc.)

Checklist

• Code contributed by me aligns with current project license: Apache 2.0
• I Added CHANGELOG entry regarding this change
• I have implemented unit tests to cover my changes
• I have added/updated the javadocs and other documentation accordingly
• No new bugs, code smells, etc. in SonarCloud report
• I tested my code in Kubernetes
• I tested my code in OpenShift

[sonarqubecloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud