fix: wait for CRDs to be Established in OpenShift E2E workflow

Resolves #277. The previous check used `kubectl get crd` to verify CRD
existence, which was redundant since a successful `kubectl apply` already
guarantees that. What actually needs checking is that the CRDs become
"Established", meaning the API servers have digested the definitions.

Replace the existence checks with `kubectl wait --for=condition=Established`
calls (60s timeout) for each of the three FMA CRDs.

Signed-off-by: Mike Spreitzer <mspreitz@us.ibm.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: MikeSpreitzer

.github/workflows/ci-e2e-openshift.yaml

@@ -443,12 +443,12 @@ jobs:
             fi
           done
 
-          # Verify CRDs are registered
-          echo "Verifying CRDs..."
-          kubectl get crd inferenceserverconfigs.fma.llm-d.ai
-          kubectl get crd launcherconfigs.fma.llm-d.ai
-          kubectl get crd launcherpopulationpolicies.fma.llm-d.ai
-          echo "All CRDs registered successfully"
+          # Wait for CRDs to become Established (API servers have digested the definitions)
+          echo "Waiting for CRDs to become Established..."
+          kubectl wait --for=condition=Established crd/inferenceserverconfigs.fma.llm-d.ai --timeout=60s
+          kubectl wait --for=condition=Established crd/launcherconfigs.fma.llm-d.ai --timeout=60s
+          kubectl wait --for=condition=Established crd/launcherpopulationpolicies.fma.llm-d.ai --timeout=60s
+          echo "All CRDs established"
 
       - name: Create ConfigMaps
         run: |