Use gitlab-qa version ~> 4.0

What does this MR do?

In support of any MR that might need dependency to a custom version of gitlab-qa, this change limits the runs to using ~> 4.0.

This change also updates outdated gems.

Reasoning:

If you are working on a change in gitlab which has a dependency on a gitlab-qa change, this allows us to push a test gitlab-qa gem and specify

gem 'gitlab-qa', 'my-test-gem'

Which would allow our MR to run a pipline against the gem. Of course, before merging it'd be necessary to revert. Purely for testing in pipelines.

Does this MR meet the acceptance criteria?

Conformity

• [-] Changelog entry
• [-] Documentation created/updated or follow-up review issue created
• Code review guidelines
• Merge request performance guidelines
• Style guides
• [-] Database guides
• [-] Separation of EE specific content

Availability and Testing

This change will allow future gitlab-qa test gems to be pushed and tested against without fear of breaking the main pipeline