Paginate group runners in CI/CD settings

What does this MR do and why?

This change prevents large group runner datasets from impacting performance in the CI/CD settings page by enabling paginating them.

Users will be able to locate group runners in the list via pagination.

A small font size issue in the available runners label is fixed as well

Changelog: fixed

Screenshots or screen recordings

before	after

How to set up and validate locally

We are verifying a project that belongs to a group (is not a user namespace). Find a project like that: e.g. /flightjs/Flight

Prepare your environment

We need over 20 group runners to check the pagination:

1. Visit your project's group
2. Go to Group -> CI/CD -> Runners
3. Check if you have Group Runners in the list, if not create at least 21.

Use these command to create them

1. Install gitlab-runner with

$ brew install gitlab-runner

1. Get the runner registration token from the UI:

1. Replace $RUNNER_TOKEN with your token in the command below, and repeat the command as needed:

$ gitlab-runner register --url http://gdk.test:3000/ --registration-token $RUNNER_TOKEN --executor shell --description instance-runner-$(gdate "+%s-%3N") -n

Ensure the runners are created by refreshing the page.

Check the pagination in the project page

1. In your project projects, visit
2. Visit Settings -> CI/CD
3. Open Runners
4. Verify the pagination to see multiple lists of Group Runners works.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #334285 (closed)