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_cgp/models/fp_cgp_registration.py

@@ -19,7 +19,7 @@ class FpCgpRegistration(models.Model):
     so this record lives on ``res.company``.
     """
     _name = 'fusion.plating.cgp.registration'
-    _description = 'Fusion Plating — CGP Registration'
+    _description = 'Fusion Plating - CGP Registration'
     _inherit = ['mail.thread', 'mail.activity.mixin']
     _order = 'registration_date desc, id desc'
 
@@ -27,7 +27,7 @@ class FpCgpRegistration(models.Model):
         string='Reference',
         required=True,
         tracking=True,
-        help='Label for this registration, e.g. "Acme Plating — CGP Reg."',
+        help='Label for this registration, e.g. "Acme Plating - CGP Reg."',
     )
     company_id = fields.Many2one(
         'res.company',