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

@@ -80,7 +80,7 @@
                                    string="Outbound Shipment"/>
                         </button>
                         <!-- CoC smart button → cert record (not the
-                             raw PDF — operator can print/reset/void
+                             raw PDF - operator can print/reset/void
                              from the cert form). -->
                         <button name="action_view_coc"
                                 type="object"
@@ -187,7 +187,7 @@
                             </div>
                             <div class="mt-1 small text-muted">
                                 <field name="assigned_driver_id"/>
-                                <span t-if="record.vehicle_id.raw_value"> — <field name="vehicle_id"/></span>
+                                <span t-if="record.vehicle_id.raw_value"> - <field name="vehicle_id"/></span>
                             </div>
                             <div class="mt-2" t-if="record.tdg_required.raw_value">
                                 <span class="o_fp_badge" data-state="tdg">TDG</span>