GitLab Runner version updates of Hosted Runners for GitLab.com

An issue to track a record of when and which shards we've been updating. Until we will get a full automated mechanism (maybe triggered from GitLab Runner main merges, maybe somehow else), that's something we need to keep doing manually.

And for that we'd like to track what and when happened and estimate how much time we're spending on these tasks.

Versions for the published packages - both the tagged releases and the pre release that we use for our hosted runners - are now automatically published by GitLab Runner release pipeline into https://gitlab.com/gitlab-org/gitlab-runner/-/wikis/Released-runner-versions.

When preparing to execute another version update, check what's the newest available version there!

Please also start by preparing an entry for the new version in a comment below by opening a new thread using the following template:

# Version `RUNNER_VERSION`

Commit SHA: [RUNNER_COMMIT_SHA](https://gitlab.com/gitlab-org/gitlab-runner/-/commits/RUNNER_COMMIT_SHA)

Check package link: [RUNNER_VERSION](https://packages.gitlab.com/app/runner/unstable/search?q=RUNNER_VERSION-1_amd64&filter=all&filter=all&dist=ubuntu)

| Updated shards | Date of execution | Chef-repo MR |
|----------------|-------------------|--------------|
| private<br/>saas-macos-staging | YYYY-MM-DD | link-to-the-chef-repo-mr+ |
| shared-gitlab-org<br/>saas-linux-small-amd64<br/>saas-linux-small-arm64<br/>saas-linux-medium-amd64<br/>saas-linux-medium-amd64-gpu-standard<br/>saas-linux-medium-arm64<br/>saas-linux-large-amd64<br/>saas-linux-large-arm64<br/>saas-linux-xlarge-amd64<br/>saas-linux-2xlarge-amd64 | YYYY-MM-DD | link-to-the-chef-repo-mr+ |
| saas-macos-medium-m1<br/>saas-macos-large-m2pro | YYYY-MM-DD | link-to-the-chef-repo-mr+ |