Resources for discovered apps should be restored once PVC/PV restore is complete and it's state is Primary

[ShyamsundarR]

For declarative applications, the DRPC controls the roll out of the application once VRG reports DataReady and status.State as Primary (and also ClusterDataReady as true). This ensures that the volumes are primary and ready to use before a pod attempts to map/mount the PVC.

In the case of discovered apps, the app resources are restored right after PVC/V restore, without waiting for their state to reach Primary. This can cause unwanted errors in pod startups ("volume is not primary yet"), etc. There are also cases where sequencing this is better than letting it eventually reconcile, avoids races between storage promoting the volume and attempting to stage it.

The ask in this issue is to sequence the restores, and wait for restored PVC/PV to report as Primary before restoring other k8s resources.