Check Bloomerang donors against NetSuite customers

**Objective:** Check whether Bloomerang constituents matching `{constituent-name}` have a matching NetSuite customer record, using email as the key. Look at up to `{max-records}` constituents (default 25).

**Step 1: Find the constituents (Bloomerang)**

Call `bloomerang-get-constituent` with `full-name.contains` set to `{constituent-name}` and `max-records` set to `{max-records}`. Keep `id`, `account-number`, `full-name`, `type`, `status` and `primary-email` for each. If nothing is returned, say so and stop.

**Step 2: Find the customer for each (NetSuite)**

For each constituent that has a `primary-email`, call `netsuite-get-customer` with `email` set to that value. If a constituent has no email, call `netsuite-get-customer` with `name.contains` set to the `full-name` and mark the match as weak (name only).

**Step 3: Report**

Return a table with one row per constituent: Bloomerang id, account number, name, email, NetSuite customer `internal-id`, NetSuite `name`, `balance`, and a Match column with one of: Matched (email), Weak match (name only), Not in NetSuite, Several NetSuite customers. Then list the constituents with no NetSuite customer and the NetSuite customers whose name differs from the constituent name.

**Rules & Guidelines:**

* Tools whose names start with netsuite are on the NetSuite server and tools whose names start with bloomerang are on the Bloomerang server. If either server is not connected, say which one and stop.
* Compare emails case-insensitively and ignore leading and trailing spaces.
* Do not call any add or update tool on either server (the NetSuite and Bloomerang tools named add-... or update-...). This prompt only reads.

**Validation:**

* If a name search returns several customers, list them and do not pick one.
* If the two systems disagree on the name for the same email, report both spellings.