Paginate unit test report

What does this MR do?

For #280512 (closed)

This MR paginates the rows of the test suite table in the Unit Test Report to improve its performance.

Currently we render every test case in the suite to the DOM, which can make the page slow down considerably and even become non-responsive with large test suites (like GitLab's own jest suite for example 😅). This MR adds frontend-only pagination, which limits the number of rows rendered to the DOM to 20, and adds page navigation at the bottom of the table.

Screenshots

new pagination at the bottom of the Tests tab on the Pipeline page

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