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_aerospace/models/fp_config_item.py

@@ -15,7 +15,7 @@ class FpConfigItem(models.Model):
     revision, and a change history log for traceability.
     """
     _name = 'fusion.plating.config.item'
-    _description = 'Fusion Plating — Configuration Management Item'
+    _description = 'Fusion Plating - Configuration Management Item'
     _inherit = ['mail.thread', 'mail.activity.mixin']
     _order = 'name, id'
 
@@ -37,7 +37,7 @@ class FpConfigItem(models.Model):
     current_revision = fields.Char(
         string='Current Revision',
         tracking=True,
-        help='The revision currently in effect — usually the most '
+        help='The revision currently in effect - usually the most '
              'recently approved change.',
     )
     approved_by_id = fields.Many2one(