Create flaky test issues after retry in new process

From Draft to Ready

• gitlab-org/ruby/gems/gitlab_quality-test_tooling!121 (merged) is merged
• !140998 (99344a4c) is removed
• The Proof of work section is filled in

Context

Closes #428767 (closed)

What does this MR do and why?

Create issues in https://gitlab.com/gitlab-org/quality/engineering-productivity/flaky-tests to track flaky tests that were successful after a retry in a new RSpec process.

What I did outside of this MR

• I created the https://gitlab.com/gitlab-org/quality/engineering-productivity/flaky-tests project
• I created the RAILS_FLAKY_TEST_PROJECT_TOKEN project access token, with api permission and maintainer role.
  • I created gitlab-org/quality/engineering-productivity/team!142 (merged) to add the project access token to the credentials rotation docs
• I added the RAILS_FLAKY_TEST_PROJECT_TOKEN (masked, not protected) CI/CD variable to gitlab-org/gitlab

Proof of work

The MR pipelines for this MR created 31 flaky tests issues

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

Numbered steps to set up and validate the change are strongly suggested.