Detect drift when using kubectl edit and autosync is disabled

[akessner-github]

I work with people who are stuck in their ways. They refuse to stop using kubectl edit or lens to make changes. We also don't want resources to be autosynced. Instead they want to see the drift and if the drift is good, update git to match the change, or if they don't like the change, then sync with the current git data.

What are the combination of settings that we need so that we can ensure that argoCD uses the current state of the resources in the cluster when polling every 2-3 minutes to look for changes, and not just relying on the last modified timestamp?

We are using ArgoCD version 3.0.x