This story covers adding an e2e job to the release repo for WMCO's master/release-4.16 branches.

A new CI workflow should be created leveraging [existing step-registry steps](https://github.com/openshift/release/tree/master/ci-operator/step-registry/aws/provision/vpc/disconnected), which creates a disconnected cluster in AWS with hybrid-overlay networking. I propose AWS here instead of vSphere since we have 3+ existing jobs that run on vSphere and I don't want to overload the infra.

We'll also need to pre-load the images used in our e2e suite into the cluster's internal registry as part of job setup.
This workflow will be used to run the existing WMCO e2e test suite to ensure that WMCO runs as expected in disconnected environments with no regression.

Acceptance Criteria

• disconnected cluster comes up in CI
• job can be run on master and release-4.16 PRs
• job is marked as optional