Match a Bugsnag release to the code behind it

**Objective:** Trace the Bugsnag release for app version {app-version} in project {project-name} back to the Azure DevOps commits and builds that produced it, looking at up to {max-records} records per call (default 20).

**Step 1: Find the release (Bugsnag)**

Call `bugsnag-get-release` with `app-version` and `project-name`. If nothing matches, report that and stop. Note `source-control-revision`, `build-label`, `release-date`, `errors-introduced-count` and `release-stage-name`.

**Step 2: Find the commit (Azure DevOps)**

If `source-control-revision` is present, call `azure-devops-get-commit` with `commit-id` set to it (try the full hash, then a prefix). Report author, comment, author-date and repository. If it is empty or nothing matches, say the revision is missing or unknown to Azure DevOps and continue.

**Step 3: Find the build and release (Azure DevOps)**

Call `azure-devops-get-build` and look for a build whose build-number matches `build-label` or `app-version`; if the commit repository is known, also pass `repository-id`. Then call `azure-devops-get-release` with `name.contains` set to the app version. Report the build result fields, finish-time and any matching release.

**Step 4: Report**

One section per system: the release, the commit, the build, the release record, then a line saying how well the two systems agree (same revision, same date, or no match).

**Rules & Guidelines:**

* Tools prefixed azure-devops are on the Azure DevOps server; tools prefixed bugsnag are on the Bugsnag server. Both must be connected.
* Read-only job. Never call `bugsnag-link-error-issue`, `bugsnag-create-error-issue`, `bugsnag-assign-error`, `bugsnag-fix-error`, `bugsnag-ignore-error`, `bugsnag-discard-error`, `bugsnag-open-error`, `bugsnag-update-error-severity`, `bugsnag-update-project`, `bugsnag-add-project` or `bugsnag-add-project-collaborator`. The Azure DevOps server has no write tools.

**Validation:**

* If the Bugsnag release has no source control revision, say the join falls back to version text and mark matches as low confidence.
* If several builds match, list them and do not pick one.