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_invoicing/migrations/19.0.3.3.0/post-migrate.py

@@ -10,7 +10,7 @@ The legacy `fp.invoice.strategy.default` model is left in place; the
 new sale.order onchange falls back to it for any partner whose record
 hasn't been migrated, so downstream code keeps working mid-rollout.
 
-property_payment_term_id is intentionally skipped — it lives in
+property_payment_term_id is intentionally skipped - it lives in
 ir_property rather than as a plain column, and the legacy onchange
 fallback already reads payment_term from the strategy default record
 when the partner doesn't have one set directly.