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_bridge_documents/data/documents_folder_data.xml

@@ -15,7 +15,7 @@
 <odoo noupdate="1">
 
     <record id="documents_folder_plating_quality" model="documents.document">
-        <field name="name">Plating — Quality</field>
+        <field name="name">Plating - Quality</field>
         <field name="type">folder</field>
         <field name="folder_id" eval="False"/>
     </record>

fusion_plating/fusion_plating_bridge_documents/data/documents_tag_data.xml

@@ -7,11 +7,11 @@
     Tags used by the bridge to categorise mirrored quality attachments.
 
     Odoo 19 EE organises tags under a two-level hierarchy:
-      documents.facet  (a.k.a. "category" — scoped to a folder/workspace)
+      documents.facet  (a.k.a. "category" - scoped to a folder/workspace)
         └── documents.tag  (individual tags, required to have a facet_id)
 
-    We create one facet called "Record Type" inside the Plating — Quality
-    workspace, then four tags beneath it — one per supported quality
+    We create one facet called "Record Type" inside the Plating - Quality
+    workspace, then four tags beneath it - one per supported quality
     record type.
 -->
 <odoo noupdate="1">