Rely on Eventual Consistency while creating application resources

# Summary

**ArgoCD fails in some scenarios and requires manual intervention.**

For e.g. - it is given to create resources `A`, `B`, `C` and `D`. It will try to create those resources in only 1 order - `A | B | C | D`.

But what if in order to create `A`, `C` needs to exist? ArgoCD will fail in that case, with the above order.

This is because ArgoCD doesn't try all possible orders in which those resources can be created. Rather it tries only one and then fails. Currently, to solve this kind of problem, we need ArgoCD sync waves, hooks etc.

# Motivation

Please give examples of your use case, e.g. when would you use this.

# Proposal

Implement **eventual consistency** like CrossPlane (CrossPlane tries all possible orders of creating given resources).

> NOTE - Create an alert that if synchronization error persists even after x amount of time, it means there is some serious issue other than the dependency problem.

Credit - https://www.youtube.com/watch?v=t1Fdse-F9Jw by @vfarcic

The issue names no files, tests, or entry points; begin by locating Argo CD's synchronization and resource-creation flow and reviewing how sync waves and hooks currently order resources. Done requires eventual-consistency handling for dependency-related failures, an alert when synchronization errors persist beyond a defined duration, and documented use cases.

Written by the indexing model from the issue text.