Track test failures on pipeline completion

What does this MR do?

Solves https://gitlab.com/gitlab-org/gitlab/-/issues/281723

We want to set a limit of max trackable test failures on the pipeline level. Previously, the limit of 200 is per build. This MR moves the limit of 200 on the pipeline level, thus we won't track test failures if the total number of test case failures in a pipeline exceeds the limit.

The reason behind this 200 limit is that we mainly want to track test failure history for identifying flaky specs. A suite with hundreds of failures does not signify there's a flaky spec in there anyway.

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• 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