Follow-up from "Integrate orchestrated e2e tests in to gitlab project pipeline"

The following discussions from !92039 (merged) should be addressed:

@acunskis started a discussion: (+5 comments)

@rymai @sliaquat @mlapierre This is ready for review. All tests are finally passing (except broken tests in master).

Apologies for mr being fairly large, it involved quite a bit renamings which probably could have been implemented separately but oh well, it's too late now 😄

cc: @balasankarc just FYI since it changes how gitlab will interact with gitlab-omnibus-mirror pipeline a bit, mainly not needing for omnibus to trigger tests anymore.

#   * feature flag changed - runs full test suite with base gitlab instance configuration with both ff states
#   * feature flag deleted - runs only ee:instance job

@sliaquat started a discussion:

#   * only e2e spec files changed - runs only changed specs
#   * MR has DevOps stage label - runs only changed specs for the stage

@sliaquat started a discussion:
Because we are not listing edge cases (eg. MR has stage label but also QA framework changes):
```
# At a high level, selective test execution against omnibus instance have following execution scenarios:
```
@sliaquat started a discussion:

Should this be renamed to .qa:rules:package-and-test?
@sliaquat started a discussion:

Should this be renamed to .qa:rules:determine-e2e-tests?

@sliaquat started a discussion:

    - <<: *if-dot-com-gitlab-org-and-security-merge-request-manual-ff-package-and-e2e
The definition on line 137 should also be renamed.

@sliaquat started a discussion:
```
.qa:rules:package-and-e2e:
```
(Including all references)

Edited Aug 30, 2022 by andrey