Trace any Bugsnag release to its GitHub commit and build

**Objective:** For the Bugsnag project `{project-name}`, identify the GitHub commit and workflow run behind release `{app-version}` (default: the most recent release) and report them alongside the release's health.

**Step 1: Find the release in Bugsnag**

Call `bugsnag-get-release` with `project-name` set to `{project-name}`. If `{app-version}` is given, also filter by `app-version`; otherwise take the release with the latest `release-date`. If more than one release matches (for example the same version in several release stages), list them with their release-stage-name and stop, asking which one to trace.

Record app-version, release-date, release-stage-name, build-label, source-control-revision, errors-introduced-count, errors-seen-count, sessions-count-in-last-24h and unhandled-sessions-count.

**Step 2: Carry the revision to GitHub**

If source-control-revision is empty, report that the release was not uploaded with source control information and stop after printing the release detail. Otherwise call `github-get-commit` with `sha` set to the source-control-revision. Bugsnag may store a short or full SHA: if the exact filter returns nothing and the revision is shorter than 40 characters, call `github-get-commit` with `commit-date.from` and `commit-date.to` spanning the two days before release-date and match on a sha that starts with the revision.

**Step 3: Find the workflow run**

Call `github-get-workflow-run` with `created-date.from` and `created-date.to` spanning the two days before release-date. Keep the runs whose sha equals the commit sha from Step 2.

**Step 4: Report**

* Release: app-version, release stage, release date, build label
* Commit: sha, author-name, commit-date, first line of message, url
* Workflow run(s): name, run-number, branch, conclusion, url
* Health: errors introduced, errors seen, sessions in the last 24h, unhandled sessions

**Rules & Guidelines:**

* `bugsnag-get-release` is on the bugsnag server. `github-get-commit` and `github-get-workflow-run` are on the github server.
* This is read-only. Do not call any Action tool on either server, including `github-rerun-workflow-run`, `github-cancel-workflow-run`, `github-add-issue` and `bugsnag-update-project`.

**Validation:**

* If no release matches, say so and list the three most recent releases for the project.
* If the revision is not found in GitHub, report the release as present in Bugsnag with no matching commit in the connected repository, and note that the repository may be a different one.
* If no workflow run matches the sha, report the commit without a run rather than guessing a nearby run.