Adoption to RHOSO 18.0 from Director Operator based deployments OSP17.1
Director Operator deployment is running on an existing OCP cluster. When customers would like to adopt to 18.0 they will most likely perform the adoption procedure on the same OCP cluster.

Acceptance criteria:

1. Verify the adoption process functionallity on separated OCP cluster in order to reduce complexity from automation and infrastructure.
2. Verify the adoption process on the same OCP cluster
3. The regular tempest tests run in OSPdO should pass before and after adoption.

While it is simpler to adopt (and automate the adoption process) with a single cluster, testing this process automatically requires significant reworking some of our test tooling and Infrastructure(CIFW and install-yamls) that hasn't been tested before.

This has depndency on the triplo-ci-internal zuul definitions repo for infrastructure and the dataplane-adoption repo for adoption process and adoption verification itself.