increase status test timeouts for OCP deployment

[xtophd]

part of the playbooks finishing process that

• watches the cluster deployment progress,
• checks for nodes ready,
• checks for and approves CSR requests,
• checks for clusteroperator availability,
• etc ...

the timeouts are apparently too short for OCP 4.7.

also note that even previously the timeouts are too short for deployments with very slow download links.

3 major issues to consider:

• if timeouts expire and playbooks exit during the bastion buildout (ie: during downloads), the automated deployment ends in failure
• if timeouts expire and playbooks exit during the wait for "nodes ready", the automated detecting and approval of CSR requests ends and the automated deployment ends, but is manually recoverable
• if timeouts expire while waiting for "clusteroperators available", the playbooks end with a failure but the cluster will continue to deploy until successful (probably).

[xtophd]

one possibility is to add a set of unique timer values to the openshift version config. individual users could then modify a multiplier parameter in the master-config.yml to alter default values to something more accommodating to their environment.