Add upgrade status badges in runners

What does this MR do and why?

Depends on !91682 (merged) and !91554 (merged)

Adds 2 "runner outdated" counters to indicate to users they should update their runners.

Screenshots or screen recordings

mobile	desktop

How to set up and validate locally

This feature is a bit complicated to setup but you can skip some steps depending on what you want to review:

Creating an outdated runner and recalculating it's outdated:

You can skip these first instructions if you simply want to see the user flow, but you may see 0 in the counts

1. Have at least one runner that needs an upgrade registered (a couple of versions behind)
   • If you use brew to install gitlab-runner, you can use these commands to swap versions, after that run your runner:
   • In my system, I run my old version like this: /usr/local/opt/gitlab-runner@14.10.0/bin/gitlab-runner@14.10.0 run

Finding the outdated runner:

1. Have a GitLab Ultimate license
2. Go to the runner details in Admin -> Runners
3. Check "outdated" results

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