E2E test: remove airborne from elasticsearch tests
What does this MR do and why?
Removes the usage of airborne from elasticsearch E2E tests. This is to prevent confusion over whether to use airborne or Support::API. When we have both and we aren't explicit, it can lead to issues when the wrong module is invoked. e.g:
Partially addresses gitlab-org/quality/quality-engineering/team-tasks#1115 (closed)
I've also been explicit when using Support::API for requests.
Passing test results: https://gitlab.com/gitlab-org/gitlab/-/jobs/7725591541
Note: there is a test that seems to fail the first attempt, but this is the same as in master, e.g. https://gitlab.com/gitlab-org/gitlab/-/jobs/7718584322#L655
MR acceptance checklist
This updates a number of orchestrated tests so it is probably more efficient to look at pipeline results.
Edited by Jay McCure