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_quality/models/fp_quality_reason.py

@@ -3,14 +3,14 @@
 # License OPL-1 (Odoo Proprietary License v1.0)
 # Part of the Fusion Plating product family.
 #
-# Sub 12 Phase B — quality reason (root-cause classification library).
+# Sub 12 Phase B - quality reason (root-cause classification library).
 
 from odoo import fields, models
 
 
 class FpQualityReason(models.Model):
     _name = 'fp.quality.reason'
-    _description = 'Fusion Plating — Quality Reason'
+    _description = 'Fusion Plating - Quality Reason'
     _order = 'category, name'
 
     name = fields.Char(required=True, translate=True)