E2E test: remove airborne from non ee api tests
What does this MR do and why?
Removes the usage of airborne from non-ee api 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 resolves gitlab-org/quality/quality-engineering/team-tasks#1115 (closed)
I've also been explicit when using Support::API for requests.
How to set up and validate locally
Tests passing:
One of the modified tests runs on staging only, so I have run the gitlab-qa image from this MR against staging here: https://ops.gitlab.net/gitlab-org/quality/staging/-/jobs/15097132#L308
Edited by Jay McCure