Refactor runner list empty states

What does this MR do and why?

Technical improvement before implementing #410602 (closed).

This internal change splits the implementation of the empty statue in two. The goal is to allow us to display them independently depending on the current runner state.

Screenshots or screen recordings

No changes are expected, these are the two variants we are displaying:

No runners at all	No runners found

How to set up and validate locally

1. You may input a filtered search in Admin -> Runners.
2. You may visit a group that has no runners attached.

We have a comprehensive suite of tests for admin and groups, they are written like this:

it_behaves_like 'shows no runners registered'

it_behaves_like 'shows no runners found'

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 #410602 (closed)

changed milestone to %16.1

added RunnerP2 Seeking community contributions UI polish UX [Deprecated] Category:Runner Fleet devopsverify grouprunner maintenanceusability sectionops severity2 typemaintenance workflowready for development + 1 deleted label

assigned to @mrincon

Please wait for Reviewer Roulette to suggest a designer for UX review, and then assign them as Reviewer. This helps evenly distribute reviews across UX.

This message was generated automatically. You're welcome to improve it.

changed the description

added frontend label

1 Warning

There were no new or modified feature flag YAML files detected in this MR. If the changes here are already controlled under an existing feature flag, please add the feature flagexists. Otherwise, if you think the changes here don't need to be under a feature flag, please add the label feature flagskipped, and add a short comment about why we skipped the feature flag. For guidance on when to use a feature flag, please see the documentation.

	1 Message
	CHANGELOG missing: If you want to create a changelog entry for GitLab FOSS, add the Changelog trailer to the commit message you want to add to the changelog. If you want to create a changelog entry for GitLab EE, also add the EE: true trailer to your commit message. If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

Reviewer roulette

Changes that require review have been detected!

Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:

Category	Reviewer	Maintainer
frontend	Miranda Fluharty (@mfluharty) (UTC-6, 8 hours behind @mrincon)	Phil Hughes (@iamphill) (UTC+1, 1 hour behind @mrincon)
UX	Camellia X. Yang (@cam.x) (UTC+0, 2 hours behind @mrincon)	Maintainer review is optional for UX

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

Bundle size analysis [beta]

This compares changes in bundle size for entry points between the commits 121e43ec and 1686cd90

Special assets

Entrypoint / Name	Size before	Size after	Diff	Diff in percent
average	4.13 MB	4.13 MB	-	0.0 %
mainChunk	2.97 MB	2.97 MB	-	0.0 %

---

Note: We do not have exact data for 121e43ec. So we have used data from: 4e0125b2.
The target commit was too new, so we used the latest commit from master we have info on.
It might help to rerun the bundle-size-review job
This might mean that you have a few false positives in this report. If something unrelated to your code changes is reported, you can check this comparison in order to see if they caused this change.

Please look at the full report for more details

---

Read more about how this report works.

Generated by Danger

Allure report

allure-report-publisher generated test report!

e2e-test-on-gdk: test report for 1686cd90

expand test summary

+-----------------------------------------------------------------------+
|                            suites summary                             |
+------------------+--------+--------+---------+-------+-------+--------+
|                  | passed | failed | skipped | flaky | total | result |
+------------------+--------+--------+---------+-------+-------+--------+
| Create           | 8      | 0      | 1       | 0     | 9     | ✅     |
| Monitor          | 4      | 0      | 0       | 0     | 4     | ✅     |
| Manage           | 1      | 0      | 0       | 0     | 1     | ✅     |
| Plan             | 4      | 0      | 0       | 0     | 4     | ✅     |
| Data Stores      | 2      | 0      | 0       | 1     | 2     | ❗     |
| Framework sanity | 0      | 0      | 1       | 0     | 1     | ➖     |
| Govern           | 2      | 0      | 0       | 0     | 2     | ✅     |
+------------------+--------+--------+---------+-------+-------+--------+
| Total            | 21     | 0      | 2       | 1     | 23    | ❗     |
+------------------+--------+--------+---------+-------+-------+--------+

e2e-review-qa: test report for 1686cd90

expand test summary

+-----------------------------------------------------------------------+
|                            suites summary                             |
+------------------+--------+--------+---------+-------+-------+--------+
|                  | passed | failed | skipped | flaky | total | result |
+------------------+--------+--------+---------+-------+-------+--------+
| Verify           | 10     | 0      | 0       | 0     | 10    | ✅     |
| Create           | 6      | 2      | 1       | 0     | 9     | ❌     |
| Framework sanity | 0      | 0      | 1       | 0     | 1     | ➖     |
| Plan             | 3      | 0      | 1       | 2     | 4     | ❗     |
| Manage           | 1      | 0      | 0       | 0     | 1     | ✅     |
| Data Stores      | 2      | 0      | 0       | 1     | 2     | ❗     |
| Monitor          | 4      | 0      | 0       | 0     | 4     | ✅     |
| Govern           | 2      | 0      | 0       | 1     | 2     | ❗     |
+------------------+--------+--------+---------+-------+-------+--------+
| Total            | 28     | 2      | 3       | 4     | 33    | ❌     |
+------------------+--------+--------+---------+-------+-------+--------+

There are some test failures that need attention

removed Seeking community contributions label

closed