Argo CD should detect unknown fields in invalid specs as OutOfSync

[jessesuen]

If a user has the following in their git repo, we will not detect it as OutOfSync.

apiVersion: v1
kind: ConfigMap
metadata:
  name: invalid-cm
  annotations:
    argocd.argoproj.io/sync-options: Validate=false
invalidKey: asdf

This is because we drop invalidKey as part of remarshalling/normalization when we do comparisons.

[jessesuen]

This is not a common problem, because normally kubectl apply will prevent the deploy because it fails validation. The user would notice the failed sync and fix the problem in their git repo. They would need to disable validation to get to this bug.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.