Add k6 Scenario Test for Creating a Project (POST /projects)

What does this MR do?

This MR adds a k6 scenario test to measure performance for creating a project using POST /projects endpoint.

I have run this locally against the linear queries 3k environment using 60s_60rps.json options with linear queries feature flags disabled (https://gitlab.com/gitlab-org/quality/gitlab-environment-toolkit-configs/gitlab-qa-lnr-quers).

3k_v14-10-2-ee_2022-05-11_202212_results.txt

3k_v14-10-2-ee_2022-05-11_202212_results_output.log

I have set the thresholds based on the changes made in this MR: !422 (merged) (see also Review Scenario RPS target scalar on larger envs (#509 - closed))

Related issues

• Issue for adding new test: Scenario Test for Creating a Project (`POST /pr... (#510 - closed)
• Issue for improving performance of POST /projects: Improve Performance of Create New Project API U... (gitlab-org/gitlab#362390)

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, @description, and @gpt_data_version tags with the information regarding the new test.
  • @gpt_data_version should be generally 1 unless you know the test is for data that's in a specific version.
• Create a bug if the endpoint response time is above the performance main target (200 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.