Jobs to rerun failed tests from previous pipeline's results

What does this MR do?

Adds setup and test stage jobs to detect and run failures from previous pipeline

This change aims to reduce the feedback time when resolving failed tests for a Merge Request.

The new setup stage jobs will detect the previous test files associated with failed jobs in the test stage of the previous pipeline and create a file with a list.

The test stage jobs will execute a rerun based on those detected test files.

How to setup and validate locally (strongly suggested)

It is possible to add the variables to run this locally via the pipeline script initiated in the new setup stage job. However, the script aims to locate the previous pipeline to the one currently running, so if this is executed outside of the CI context the second most recent pipeline for any MR would be detected.

Does this MR meet the acceptance criteria?

Conformity

• I have included changelog trailers, or none are needed. (Does this MR need a changelog?)
• I have added/updated documentation, or it's not needed. (Is documentation required?)
• I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
• I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
• I have self-reviewed this MR per code review guidelines.
• This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.
• This change is backwards compatible across updates, or this does not apply.

Availability and Testing

• I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.)
• I have tested this MR in all supported browsers, or it's not needed.
• I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.

Security

Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

References

Related issue: #333857 (closed)