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_logistics/models/fp_route_stop.py

@@ -15,7 +15,7 @@ class FpRouteStop(models.Model):
     stops (fuel, break) just carry an address and a planned time.
     """
     _name = 'fusion.plating.route.stop'
-    _description = 'Fusion Plating — Route Stop'
+    _description = 'Fusion Plating - Route Stop'
     _order = 'route_id, sequence, id'
 
     route_id = fields.Many2one(