fix(tools): ship types read as their family; letterless destinations are unknown

AIS sends ship types as ITU-R M.1371 codes, so vessels_in_area grouped
"70", "74" and "79" as three types, and type: "tanker" matched nothing on
feeds that send codes. Codes now read as the family the vessel cards already
show (CARGO, TANKER, TUG), for rows, group_by and the type filter. The code
table moves to src/data/vesselTypes.js, which has no i18n import, so the
server-side tools can use it; vesselLabels re-exports it.

A destination with no letters ("0", "---") now counts as unknown.

Live, Singapore: "most by type: CARGO (3), TANKER (3), PASSENGER (1)"; "how
many tankers near Singapore" found 3.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

changelog.d/1056-area-tool-breakdowns.md

@@ -4,5 +4,6 @@
   of estimating from the returned rows. Airlines come from the ICAO designator
   in each callsign (SWA1234 counts as SWA), so the breakdown works on feeds
   that report no operator; operator and type are counted only where the feed
-  reports them; AIS ship type 0 ("not available") counts as unknown
+  reports them. Ship types count by family, so AIS codes 70 to 79 are all
+  cargo, and type 0 ("not available") counts as unknown
   (quanticsoul4772, #1056).