Check NetSuite prices for any Akeneo product before it goes live

**Objective:** Show every NetSuite price for the Akeneo product with SKU {sku}, optionally limited to the price level {price-level-id}, next to the catalog record.

**Step 1: Read the catalog record (akeneo)**

Call `akeneo-get-product` with identifier set to {sku}. If it returns nothing or more than one product, report that and stop. Keep product-name, enabled, family and brand.

**Step 2: Read the prices (netsuite)**

Call `netsuite-get-item` with item-number set to the SKU to confirm the item exists and keep its internal-id and description. If it does not exist, report the product as absent from NetSuite and stop. Then call `netsuite-get-itempricing` with item-number set to the SKU, and when a price level is given, price-level-id set to {price-level-id}. Keep price-level-id, price, minimum-quantity and currency-id for each row.

**Step 3: Report**

A table of price level, minimum quantity, price and currency, lowest price first. Note whether the product is enabled in Akeneo. Flag an enabled product with no price rows, and any price of zero.

**Rules & Guidelines:**

* Tools starting akeneo- are on the akeneo server (the product catalog, PIM). Tools starting netsuite- are on the netsuite server (the ERP). Both servers must be connected.
* The join key is the Akeneo product identifier (the SKU) and the NetSuite item-number. Compare them exactly first, then trimmed and case-insensitive; report any record that only matches that loose way as a format mismatch rather than a match.
* This prompt is read-only. Never call any akeneo-add-*, akeneo-update-*, akeneo-delete-*, akeneo-submit-* or akeneo-start-* tool, and never call any netsuite-add-* or netsuite-update-* tool.
* Akeneo does not hold prices in this tool set, so do not report a price from Akeneo.

**Validation:**

* If the item descriptions differ noticeably between the two systems, show both and say so.
* If several currencies appear, do not add or compare them across currencies.