See which open Bugsnag errors have no Jira issue

**Objective:** For Bugsnag project {bugsnag-project-name}, report which open errors of severity {severity} are tracked in Jira project {jira-project-key} and which are not. Read-only.

**Step 1: List the open errors (bugsnag server)**

Call `bugsnag-get-error` filtered by project-name {bugsnag-project-name}, status open, and severity {severity} (default error when not supplied). Keep error-id, error-class, message, events, users, last-seen-date and error-url. If nothing comes back, report that the project has no open errors at that severity and stop.

**Step 2: Look for the Jira side (jira server)**

For each error, in order, most events first:

* Call `jira-get-issue-remote-link` filtered by global-id set to that error id. A hit means the error is tracked, and link-title tells you what it was filed as.
* If there is no hit, call `jira-get-issue` filtered by project-key {jira-project-key} and summary containing the error id. This catches issues raised before the remote link convention existed.
* If neither finds anything, the error is untracked.

Note that `jira-get-issue-remote-link` does not report which issue a link belongs to, so use the `jira-get-issue` lookup whenever you need to name the issue key.

**Step 3: Report**

Two tables.

* Tracked: error class, event count, affected users, last seen, and the Jira issue key where you could determine it.
* Untracked: error class, message, event count, affected users, last seen, error url.

Sort both by event count descending. End with one line naming the untracked error with the highest event count as the one to raise first.

**Rules & Guidelines:**

* `bugsnag-get-error` is on the bugsnag server. `jira-get-issue` and `jira-get-issue-remote-link` are on the jira server. Both servers, plus this one, must be connected.
* This prompt is read-only. Do not call `jira-add-issue`, `jira-add-issue-comment`, `jira-add-issue-remote-link`, `jira-update-issue`, `bugsnag-fix-error`, `bugsnag-ignore-error`, `bugsnag-discard-error` or `bugsnag-link-error-issue`.
* Do not guess at a match from the wording of an issue summary. A match is the error id appearing as a remote link global id or in the issue summary, nothing looser.

**Validation:**

* If Jira returns nothing at all for the project key, say whether that is because the key is wrong rather than reporting every error as untracked.
* If an error id matches a remote link but no issue summary, report it as tracked with the issue key unknown, and say the link exists but the issue could not be named.