[Feature] Ability to control the `main-ssh-readiness-aos-cmd` and `main-ocp-readiness-aos-cmd` timeouts

[kpouget]

To be able to integrate the mapt AWS deployment of CRC SNC in my CI performance test harness, I would need to be able to control the duration of the timeout for these two steps (at least):

• main-ssh-readiness-aos-cmd
• main-ocp-readiness-aos-cmd

and/or stop before them, and let my CI automation handle the SSH and OCP wait.

[anjannath]

i think we can add some kind of flag for the mapt openshift-snc aws create command --ssh-readiness-timeout --ocp-readiness-timeout

[adrianriobo]

or even if you want the 2nd approach to --disable-readiness to full disable them

[kpouget]

yes, overall the ability to control the timeout and disable some steps seem useful.
For my automation,

--ssh-readiness-timeout XX --disable-ocp-readiness

or

--disable-readiness

would be equivalent, the second one would just require an extra task to perform the ssh readiness wait, which is fine.

And that's linked with #629, as the relevant credentials have to be generated before the SSH early exist