[E2E] Do not create runner resources in parallel
What does this MR do and why?
As an alternative solution to the problem identified in !144588 (closed) we could consider just not creating this problematic resource in parallel which we review the underlying problem.
This addresses the concern that I initially considered reverted a fix that was implemented to help resource cleanup. gitlab-org/quality/quality-engineering/team-tasks#2407 (comment 1756559299)
There's been an uptick in failures in Verify Project artifacts when user tries bulk deletion successfully delete them since this MR was merged.
I noted that this test specifically uses some Parallel threads to start runners and I suspect that something in the MR doesn't account for that.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
How to set up and validate locally
$ bundle exec rspec qa/specs/features/browser_ui/4_verify/ci_project_artifacts/user_can_bulk_delete_artifacts_spec.rb:30