Add Releases API test

What does this MR do?

MR adds Releases API endpoint test to the GPT. This test requires new data to be added to gitlabhq project tarballs. This gitlabhq version is bumped up to 2.

Depends on:

• https://gitlab.com/gitlab-org/quality/performance-data/-/merge_requests/5
• #403 (closed)

Related issues

Closes #386

Checklist

• Ensure test data for the new endpoint is representative. We recommend using large data ("edge cases") in performance tests. The impact of optimizations is more visible on the big numbers and large data may expose more performance bottlenecks.
• Fill in @endpoint and @description tags with the information regarding the new test.
• Create a bug if the endpoint response time is above the performance main target (500 ms).
  • Specify created issue link under @issue tag.
• Consider specifying the additional @flags:
  • unsafe - required for Unsafe tests. Ensure that data before and after the test is consistent.
  • search - labels Search related tests.
  • dash_url - labels Web tests with the check if the endpoint path has a dash \ redirect.
• Web tests
  • Specify all called controller methods under the @description.
  • Consider creating MR to add the new test to GitLab Performance SiteSpeed.
• Update all Reference Architecture envs with the new gitlabhq with Releases - will be done outside of this MR
  • 1k
  • 2k
  • 3k
  • 5k
  • 10k
  • 25k
  • 50k
  • docker images - probably will be updated in a separate follow-up issue