Catch up on Bugsnag errors nobody raised in Jira

**Objective:** Find the errors on Bugsnag project {bugsnag-project-name} with at least {min-events} events (default 50) that no Jira issue in {jira-project-key} tracks, and raise issues for at most {max-issues} of them (default 5), worst first.

**Step 1: Find the candidates (bugsnag server)**

Call `bugsnag-get-error` filtered by project-name {bugsnag-project-name}, status open, and events at least {min-events}. Keep error-id, error-class, message, severity, events, users, last-seen-date and error-url. Sort by events descending. If nothing comes back, report that the project has nothing above the threshold and stop.

**Step 2: Drop the ones already tracked (jira server)**

For each candidate, call `jira-get-issue-remote-link` filtered by global-id set to that error id, and `jira-get-issue` filtered by project-key {jira-project-key} and summary containing that error id. Anything found by either is already tracked and comes out of the list.

**Step 3: Resolve the Jira target once (jira server)**

Call `jira-get-project` filtered by project-key {jira-project-key} for project-id, and `jira-get-issue-type` filtered by the same project-key and name Bug for issue-type-id. If the Bug type does not exist, list the available types and stop before writing anything.

**Step 4: Confirm the list, then create**

Show the user the untracked candidates you intend to raise, capped at {max-issues}, with event and user counts. Wait for explicit approval of the list. Then, for each approved error in turn:

* Call `jira-add-issue` once, with the project-id and issue-type-id from step 3 and a summary of the error class, a colon, the first line of the message, and a trailing marker of bugsnag: followed by the error id in square brackets.
* Call `jira-get-issue` filtered by project-key {jira-project-key} and summary containing that error id, to get the issue id.
* Call `jira-add-issue-comment` once with the event count, user count, severity, first and last seen dates, and the Bugsnag error url.
* Call `jira-add-issue-remote-link` with that issue id, url set to the error url, application-name Bugsnag, title set to the error class, and global-id set to the error id.

Stop the whole run if any of those four calls fails, and report how far you got.

**Step 5: Report**

A table of error class, event count, and the Jira issue key created. Then state how many candidates were left unraised because of the cap.

**Rules & Guidelines:**

* `bugsnag-get-error` is on the bugsnag server. `jira-get-issue`, `jira-get-issue-remote-link`, `jira-get-project`, `jira-get-issue-type`, `jira-add-issue`, `jira-add-issue-comment` and `jira-add-issue-remote-link` are on the jira server. All three servers must be connected.
* Never exceed {max-issues} issues in a run, and never raise one that was not in the approved list.
* This prompt does not touch Bugsnag state. Do not call `bugsnag-fix-error`, `bugsnag-ignore-error`, `bugsnag-discard-error`, `bugsnag-assign-error` or `bugsnag-update-error-severity`. It also does not link back from the Bugsnag side; run link-error-to-new-jira-issue for a single error when you want that link too.

**Validation:**

* Re-run the step 2 check for an error immediately before raising it if the confirmation took a while. A duplicate issue is worse than a slow run.
* If `jira-add-issue` succeeds but the read-back finds nothing, stop the whole run. Do not move on to the next error with an unverified write behind you.
* If every candidate turns out to be tracked, report that as a good result rather than lowering the threshold to find work.