Story (Required)

As a QE trying to enable CI in gitops operator repository's v1.6 branch, I want to get tests from operator-e2e repository to gitops operator repository

Background (Required)

We usually update all the testing related changes in operator-e2e repository. Now that we have started storing tests in gitops-operator repository, we need to make sure both of them are up to date. Since KuTTL tests were brought into gitops operator repository during v1.7, v1.6 branch still lacks this change. In order to enable CI in v1.6 branch, we need to have test suite copy in gitops operator repository

Out of scope

Fixing flaky tests 

Approach (Required)

Make a note of all the changes that went into release-1.6 branch in operator-e2e repository and update the same in gitops operator repository's v1.6 branch. 

Dependencies

https://issues.redhat.com/browse/GITOPS-2727 

Acceptance Criteria (Mandatory)

• gitops operator repository is up to date with latest changes made in operator-e2e repository's release-1.6 branch
• CI runs were successful on v1.6 branch

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Acceptance criteria are met