Fix ibmcloud SNO deploy by consolidating both ibmcloud SNO/MNO to use…

[akrzos]

… create-ai-cluster role

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from akrzos. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[akrzos]

/test deploy-5nodes

[akrzos]

/test deploy-5nodes

[akrzos]

/test deploy-5nodes

[akrzos]

/test deploy-sno

[openshift-ci]

@akrzos: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/deploy-sno	b2fa217	link	true	/test deploy-sno

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[ebattat]

Test it on SNO IBM cloud.
/LGTM

[akrzos]

Prow jetlag ci SNO issue is related to prow scripts missing sno_use_lab_dhcp thus merging for now.