Find Bugsnag errors nobody is tracking

**Objective:** For Bugsnag project {project-name}, list open errors with at least {min-events} events (default 50) that have no matching Azure DevOps work item, checking at most {max-errors} errors (default 15).

**Step 1: Pull the errors (Bugsnag)**

Call `bugsnag-get-error` with `project-name`, `status` set to open, `events.min` set to the minimum and `max-records` set to the cap. If nothing returns, report that and stop.

**Step 2: Check each error (Azure DevOps)**

For each error call `azure-devops-get-work-item` with `title.contains` set to its error id; if empty, try its error class. Count a work item only when its title or description clearly refers to that error.

**Step 3: Report**

A table of untracked errors sorted by events descending: error-id, error-class, message (truncated), severity, events, last-seen-date, error-url. Then a short list of errors that are tracked, with the work item id and state. End with counts: checked, tracked, untracked.

**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 cap is reached, say more errors may exist.
* Mark a tracked work item in a Closed or Done state as "tracked but closed" since the error is still open in Bugsnag.