Timing out failed sync and retrying with newer commits in OpenShift GitOps

Issue

• If there is a problem with the deployment and OpenShift GitOps keeps waiting for resources forever (for example because of a misconfiguration), OpenShift GitOps is stuck in syncing status. Even if pushing a new version, OpenShift GitOps stays busy with syncing the previous version. The goal should be to prevent such a condition from happening by eventually timing out the sync after a defined period of time and with a flag to try a newer version (if available) when the sync has failed.