As a user of Argo CD on OpenShift, I want to be able to use resources of type DeploymentConfig in my managed applications. However, I noticed that the health for a DeploymentConfig is always in Healthy state, no matter the real rollout status of the resource. This makes a DeploymentConfig resource useless in combination with sync waves, or PostSync hooks

Acceptance criteria:

• A custom health check is available for resources of type apps.openshift.io/DeploymentConfig which mimics behavior of the apps.Deployment check
• The health checks reports a Progressing state if the rollout has not yet finished successfully
• The health checks reports a Degraded state if the rollout deadline limit has been exceeded