chore(plating): de-dash shipped code + intake-neutral customer emails

Replace em-dashes and en-dashes with hyphens across 789 shipped source
files (py/xml/js/scss) so the delivered module reads as human-written;
em-dashes had become a recognizable AI-generated tell. Internal .md dev
notes are excluded. The WO-sticker mojibake strippers keep their dash
search targets (now written — / –). No logic changes: comments
and display strings only; validated with py_compile + lxml parse.

Rewrite the 7 customer notification emails to be intake-neutral
(ship-in / drop-off / pickup) and repair-aware, and fix the Shipped
email documents line (packing slip vs bill of lading; certificate only
when issued). Subjects use a hyphen separator.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

fusion_plating/fusion_plating_configurator/migrations/19.0.18.11.0/post-migrate.py

@@ -3,8 +3,8 @@
 """Drop the redundant ``revision_number`` Integer column on fp.part.catalog.
 
 The model historically carried two revision fields:
-  * ``revision`` (Char, required) — the customer's actual revision label
-  * ``revision_number`` (Integer) — an internal counter
+  * ``revision`` (Char, required) - the customer's actual revision label
+  * ``revision_number`` (Integer) - an internal counter
 
 The Integer counter duplicated information already in ``revision`` and
 got out of sync whenever the customer used a non-numeric scheme