User Story:
As an OpenShift Engineer I want fix CI step to provision cluster on AWS to use dynamic Base Domain from cluster Profile to prevent failures when Test platform team batch change jobs to rebalance between AWS accounts, so we can prevent false-positive CI failures on platform external jobs.

Description:
We are observing failures across platform external CI jobs on AWS after the following PR which is changing the profile: https://github.com/openshift/release/pull/64080

*failed example: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/64021/rehearse-64021-periodic-ci-openshift-release-master-nightly-4.18-e2e-external-aws-ccm/1914507340954996736 

Currently the base domain in tied in the workflow as environment variable, required when patching the install-config. This may currently not even more required, this card will ensure this.

The recomendation is to use dynamic base domain from profile, this is one example: https://github.com/openshift/release/blob/48746e71448e3ad765e0c9f866e9980179a0951a/ci-operator/step-registry/ipi/conf/aws/ipi-conf-aws-commands.sh#L13 

Acceptance Criteria:

• platform external jobs running on AWS in Test Platform Accounts using dynamically base domain from cluster profile, preventing disruptions when Test Platform balances the jobs between AWS accounts
•  

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

issue created by splat-bot