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_nuclear/models/fp_cnsc_licence.py

@@ -11,7 +11,7 @@ class FpCnscLicence(models.Model):
 
     The Canadian Nuclear Safety Commission (CNSC) regulates all nuclear
     activities in Canada. A plating / finishing supplier that works on
-    nuclear items may hold — or be listed under — one or more CNSC
+    nuclear items may hold - or be listed under - one or more CNSC
     licences:
 
         * Class II nuclear facility licence (on-site sources,
@@ -24,7 +24,7 @@ class FpCnscLicence(models.Model):
     compliance awareness.
     """
     _name = 'fusion.plating.cnsc.licence'
-    _description = 'Fusion Plating — CNSC Licence'
+    _description = 'Fusion Plating - CNSC Licence'
     _inherit = ['mail.thread', 'mail.activity.mixin']
     _order = 'expiry_date, name'