Check open Freshdesk tickets against Jira in one table

**Objective:** For Freshdesk company `{company-id}`, list the open tickets and show which have a Jira issue and what state it is in. Look at the most recent `{max-tickets}` tickets (default 20).

**Step 1: List the company's tickets (freshdesk server)**

Call `freshdesk-get-companies` with `company-id` = `{company-id}` to get the company `name` and `account-tier`. If nothing comes back, stop and say the company was not found. Then call `freshdesk-get-tickets` with `company-id` = `{company-id}` and `max-records` = `{max-tickets}` (use 20 when empty). Keep tickets whose `status` is not resolved or closed.

**Step 2: Look each ticket up in Jira (jira server)**

For each kept ticket call `jira-get-issue` with `summary.contains` = the `ticket-id`. Take `issue-key`, `status`, `assignee` and `due-date` from any match. If there is no match, record the ticket as having no Jira issue.

**Step 3: Report**

A table sorted by ticket `priority` then `due-by`: ticket id, subject, ticket status, priority, Jira `issue-key`, Jira `status`, Jira `assignee`. Then list: (a) tickets with a Jira issue that is done while the ticket is still open, (b) high priority tickets with no Jira issue, (c) tickets that are `escalated` with no Jira issue.

**Rules & Guidelines:**

* `freshdesk-get-companies` and `freshdesk-get-tickets` are on the freshdesk server; `jira-get-issue` is on the jira server.
* Read only. Never call `freshdesk-update-ticket`, `freshdesk-add-ticket-note`, `freshdesk-reply-to-ticket`, `jira-add-issue`, `jira-update-issue` or `jira-assign-issue`.
* Matching on the ticket id in the Jira summary is a convention. Say that a missing match may only mean the issue does not follow it.

**Validation:**

* If the company has no open tickets, say so and stop.
* If a ticket matches more than one Jira issue, list all of them in that row.