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.0.0/post-migration.py

@@ -2,7 +2,7 @@
 # Copyright 2026 Nexa Systems Inc.
 # License OPL-1 (Odoo Proprietary License v1.0)
 #
-# Phase 1 multi-serial — backfill the new M2M relations from the
+# Phase 1 multi-serial - backfill the new M2M relations from the
 # pre-existing single-M2O column on sale.order.line and account.move.line.
 #
 # x_fc_serial_id was historically a stored Many2one. Phase 1 made it a
@@ -34,7 +34,7 @@ def backfill_table(cr, source_table, m2m_table, line_col):
         return
 
     # Make sure the M2M table exists (Odoo creates it on registry load,
-    # but the migration runs BEFORE the registry comes up on upgrade —
+    # but the migration runs BEFORE the registry comes up on upgrade -
     # use IF NOT EXISTS to be safe).
     cr.execute(
         f"""