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/security/fp_quality_security.xml

@@ -21,7 +21,7 @@
 
     <!-- Multi-company rule for Contract Reviews (Sub 4). -->
     <record id="fp_contract_review_company_rule" model="ir.rule">
-        <field name="name">Fusion Plating: Contract Review — multi-company</field>
+        <field name="name">Fusion Plating: Contract Review - multi-company</field>
         <field name="model_id" ref="model_fp_contract_review"/>
         <field name="global" eval="True"/>
         <field name="domain_force">[('company_id', 'in', company_ids)]</field>