Document how to handle CRD/CR race condition

[etsauer]

There is a race condition frequently created when deploying operators via OLM, where attempting to create the OperatorGroup and Subscription in the same oc apply command where the CR for that operator is also created, then the CRD for the operator hasn't yet been created. Since we don't directly create the CRD, we need to insert a conditional wait to ensure that the CRD exists before moving on.

It would also be nice if we could automate the detection of the CRDs we are waiting on, so we don't have to hardcode them in the workflow.

[etsauer]

Per @sabre1041 , here's an example command to insert between applying the OLM resources and the CR:

until oc wait --for condition=established --timeout=60s crd/argocds.argoproj.io; do sleep 2; done

[etsauer]

@sabre1041 @gnekic @jkupferer what would you say to just using a general retry loop for the entire workflow:

until oc apply -Rf simple-bootstrap/ --prune -l example.com/project=simple-bootstrap; do sleep 2; done