User Story:
As an OpenShift Engineer I want to fix the OPCT CI job by evaluating timeout increase and/or gather more cluster data to quickly identify job failure (initially caused by timeout, but env can be gone) so engineers can save time while investigating job alerts to isolate feature-specific or CI infra.

ref: nightly-4.19-opct-external-aws-ccm <https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.19-opct-external-aws-ccm/1996831003401785344|https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-[…]ter-nightly-4.19-opct-external-aws-ccm/1996831003401785344>.

Description:
< Record any background information >

Acceptance Criteria:

• gather chain added to the post stage - so standard gathering data will be collected helping any other engineers with Prow familiarity to investigate it
• new step introduced exporting OPCT namespace using must-gather (opct adm inspect ns)
• timeout increased for opct periodics - opct workflow requires much more time to complete as it runs both kube and ocp conformance

Other Information:
< Record anything else that may be helpful to someone else picking up the card >

issue created by splat-bot