Checklist:

• [*] I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• [*] I've included steps to reproduce the bug.
• [*] I've pasted the output of argocd version.

Describe the bug
We are experiencing an issue with Argo CD where rolling back an application unexpectedly alters our syncPolicy setup, specifically losing the ServerSideApply=true option.

Current Setup:

syncPolicy:
  automated: {}
  syncOptions:
    - ServerSideApply=true

After performing a rollback, we observe:

syncPolicy: {}

This prevents us from applying previous ConfigMaps as expected because the ServerSideApply flag is necessary for large ConfigMaps.

Additional Observations:

When testing rollbacks with syncPolicy:

syncPolicy:
  syncOptions:
    - ServerSideApply=true

and with auto-sync disabled, ArgoCD does not reset syncOptions, leading to a successful rollback.

To Reproduce
Configure an Argo CD application with the following syncPolicy:

syncPolicy:
  automated: {}
  syncOptions:
    - ServerSideApply=true

Perform a rollback to a previous version of the application via the Argo CD UI or CLI.

Observe that the resultant configuration is missing syncOptions.

syncPolicy: {}

Expected behavior
After rollback, the syncPolicy should remain:

syncPolicy:
  syncOptions:
    - ServerSideApply=true

Version
Taken from UI

v2.9.0+9cf0c69