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_receiving/data/delivery_carrier_seed_data.xml

@@ -9,7 +9,7 @@
     delivery_type='fixed'; Phase D will flip Purolator (and any others
     we add integrations for) to their real delivery_type.
 
-    noupdate=1 — these records are upserted once on install. Hand-edits
+    noupdate=1 - these records are upserted once on install. Hand-edits
     on the carrier records (e.g. renaming "FedEx" to "FedEx Express")
     are preserved across module upgrades.
 -->