Remove application level sync-waves

After testings, it seems we don't need to set sync-waves at the
application level. This allows to be closer to Validated Patterns
"eventually converging" practices.

Depends-On: validatedpatterns-sandbox/rhoso-gitops#17

Author: cjeanner

content/patterns/rhoso-gitops/troubleshooting.adoc

@@ -42,8 +42,8 @@ Inspect a child application that is out of sync or unhealthy:
 $ oc describe application <application-name> -n rhoso-gitops-standalone
 ----
 
-Use the Argo CD UI in the `rhoso-gitops-standalone` namespace to review sync waves,
-resource health, and diff details for upstream overlays.
+Use the Argo CD UI in the `rhoso-gitops-standalone` namespace to review
+application status, resource health, and diff details for upstream overlays.
 
 [id="rhoso-gitops-check-pods"]
 == Checking pod status
@@ -75,8 +75,8 @@ $ oc logs -n <namespace> <pod-name>
   `overrides/values-rhoso-gitops.yaml` match a tag or branch that exists in
   link:https://github.com/openstack-k8s-operators/gitops[openstack-k8s-operators/gitops].
 * *Operator install delays* — Infrastructure operators in `operator-dependencies`
-  subscribe from the cluster catalog; allow time for OLM to resolve CSVs before
-  later sync waves run.
+  subscribe from the cluster catalog; allow time for OLM to resolve CSVs.
+  Other applications retry automatically until their dependencies are satisfied.
 
 For community support, open an issue in the
 link:https://github.com/validatedpatterns-sandbox/rhoso-gitops/issues[pattern repository].

modules/rhoso-gitops/rhoso-gitops-architecture.adoc

@@ -21,13 +21,13 @@ The delivery path is:
 . Child apps sync upstream `example/*` overlays in order (operators, networks,
   control plane, dataplane)
 
-.GitOps application delivery and sync-wave ordering
+.GitOps application delivery
 image::rhoso-gitops/rhoso-gitops-applications.svg[{rhoso-gitops-pattern} GitOps application delivery,700]
 
 The diagram shows the parent Application in `vp-gitops`, child Applications in
 `rhoso-gitops-standalone`, and the upstream Kustomize overlays they sync.
-Sync-wave annotations order deployment from infrastructure operators through
-the data plane.
+All child applications deploy at sync-wave 0 and converge eventually through
+retry policies.
 
 [id="rhoso-gitops-dual-argocd"]
 == Dual Argo CD namespaces
@@ -56,44 +56,38 @@ image::rhoso-gitops/rhoso-gitops-infrastructure.svg[{rhoso-gitops-pattern} infra
 * *Data plane hosts* — one or more {rhel-short} compute nodes run {rh-rhoso-short}
   dataplane elements, connected to the control plane
 
-[id="rhoso-gitops-sync-waves"]
-== Application sync order
+[id="rhoso-gitops-deployment-convergence"]
+== Deployment convergence
 
-Child Applications deploy in sync-wave order when Argo CD reconciles the parent
-*rhoso-gitops* Application. All applications use automated sync with a retry
-policy by default.
+All child Applications deploy at sync-wave `0` (the default) when Argo CD
+reconciles the parent *rhoso-gitops* Application. Argo CD launches every child
+simultaneously; each retries (per `syncPolicy.retry`) until its upstream
+dependencies are satisfied and converges eventually.
 
-[cols="2,3,1",options="header"]
+[cols="2,3",options="header"]
 |===
-| Application | Purpose | Sync wave
+| Application | Purpose
 
 | `operator-dependencies`
 | Infrastructure operators (cert-manager, MetalLB, nmstate, observability)
-| `-20`
 
 | `openstack-operator`
 | OpenStack operator subscription
-| `-20`
 
 | `openstack-operator-cr`
 | Main `OpenStack` custom resource
-| `-15`
 
 | `openstack-secrets`
 | Secure-backend sync (disabled by default)
-| `-10`
 
 | `openstack-networks`
 | Network configuration
-| `0`
 
 | `openstack-controlplane`
 | `OpenStackControlPlane`
-| `10`
 
 | `openstack-dataplane`
 | Data plane
-| `20`
 |===
 
 After changing overrides, confirm child apps in the Argo CD UI or with