Follow-up from "Fixed outdated text" (Improve runner empty states based on permissions)

The following discussion from !93609 (merged) should be addressed:

  • @gdoyle started a discussion: (+4 comments)

    @sselhorn The language is more concise and simple, I like those changes!

    I do think that moving To register them, got to the group's Runner page into the "alert" makes the empty state less actionable and discoverable. I think the intention of that alert was to provide information about what each type of runner is (that clearly needs to be updated as it doesn't warrant a warning alert 😓).

    suggestion: Keep the empty state message separate from the informational text, as it will improve discoverability of why there are no runners and provide the user with an action.

    suggestion: Explain why there are no group runners in each scenario - I'd recommend we'd bring back the text This group does not have any group runners yet. and add the action To register them, go to the group's Runner page.. Separating the empty state message will also make it easier to plan for different messages, as it depends on the user's permission. Here are the different examples that I audited:

    Admin: If there are no group runners created yet, the message should be, This group does not have any group runners yet. Group owners can register group runners in the [group's Runners page](#link to page).

    ^^ we'd update to whatever comes of this MR

    Project maintainer: If there are no group runners created yet, the message should be, This group does not have any group runners yet. Ask your group owner to set up a group runner.

    Project maintainer: If this project is not part of a group, the message should be, This project does not belong to a group and cannot make use of group runners.

    Group owner that this project is under: If there are no group runners created yet, the message should be, This group does not have any group runners yet. Group owners can register group runners in the [group's Runners page](#link to page).

    ^^ we'd update to whatever comes of this MR