Define a roadmap for GitLab Performance Tool

The goal of the issue is to revisit existing issues and plan roadmap for GitLab Performance Tool:

• Review existing issues, close not relevant issues
• Group common issues under an epic or a label
• Explore adding a dashboard - https://gitlab.com/gitlab-org/quality/performance/-/boards/5886453
• Analyze open issues and work on the roadmap
• Document or cross-link the roadmap at https://about.gitlab.com/handbook/engineering/quality/quality-engineering/self-managed-excellence/#gitlab-performance-tool

Roadmap

Direction:

• Streamline GPT and performance test data configuration
• Expand documentation and onboard more team members to performance testing

1. Major Breaking Changes and 3.0 Refactor

• Reorganise Quality performance projects into th... (gitlab-org/quality/performance#323)
• Explore separating out GPT Data Generator into ... (gitlab-org/quality/performance#322)
• GitLab Performance Tool v3.0.0 (gitlab-org&4300)

2. Testdata improvements

• Explore using Group Exports (and Epics) in GPT ... (gitlab-org/quality/performance#354)
• Explore improving file download tests to be mor... (gitlab-org/quality/performance#366)
• Explore using project templates for small proje... (gitlab-org/quality/performance#381)
• Explore expanding the data set for git tests (gitlab-org/quality/performance#470 - closed)
• Explore expanding single data target tests to h... (gitlab-org/quality/performance#409)

3. Monitoring, Tracking, and Reporting

• Explore reporting options for endpoints that de... (gitlab-org/quality/performance#514)
• Explore track performance for multiple endpoint... (gitlab-org/quality/performance#564)
• Explore adding repo link to specific GitLab com... (gitlab-org/quality/performance#427)
• Indicate tests which passed with historical thr... (gitlab-org/quality/performance#425)

4. Documentation updates

• Update Performance page in Handbook (gitlab-org/quality/performance#182)
• Explore ways to surface docs better to increase... (gitlab-org/quality/performance#364)
• GPT Docs: Add Quickstart Guide (gitlab-org/quality/performance#273 - closed)
• Explore adding a guidance for debugging perform... (gitlab-org/quality/performance#568 - closed)

5. Onboarding more team members to GPT

• Create development and onboarding documentation, covering topics like adding tests, performance environment processes, and reviewing performance pipelines.
• Expand maintainership with new trainees

6. Picking up issues from the rest of backlog as usual