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_maintenance/views/fp_maintenance_menu.xml

@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="utf-8"?>
 <odoo>
 
-    <!-- Phase 1 — re-parented under Plating → Operations. Maintenance
+    <!-- Phase 1 - re-parented under Plating → Operations. Maintenance
          is an Operations concern, not a separate top-level. -->
-    <!-- Phase D (perms v2) — Shop Manager+ only. Operators don't need
+    <!-- Phase D (perms v2) - Shop Manager+ only. Operators don't need
          to schedule plans or browse the equipment registry. -->
     <menuitem id="menu_fp_maintenance"
               name="Maintenance"