Allows runner URLs to be fetched via a project connection

What does this MR do and why?

Allows runner URLs to be fetched via a project connection

With this change, runners our GraphQL API can provide navigation URLs to runners that are fetched via a Project.runner query.

In this way, API consumers can access these two properties:

• project.runners.edges.webUrl
• project.runners.edges.editUrl

An additional project_runners GraphQL query is added that will be used to fetch runner in the projects UI.

Changelog: added

References

• Next MR (we use these changes here): !186426 (merged)
• Related issue: #33803 (closed)
• POC of the UI !185667 (closed)

Screenshots or screen recordings

How to set up and validate locally

If you have runners visible in your project, you can issue a query for your project runners, like this one:

{
  project(fullPath: "my-group/my-project") {
    runners {
      edges {
        webUrl
        editUrl
        node { 
        	id
        }
      }
    }
  }
}

It should yield results with the corresponding webUrl and editUrl:

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.