feat(reports): packing slip in Print menu of SO, Work Order, Receiving

Generalize the delivery packing slip template to be model-agnostic
(branches on doc._name to resolve the sale order + ship-to for
sale.order / fp.job / fp.receiving / fusion.plating.delivery) and add
three report actions bound to sale.order, fp.job and fp.receiving so the
packing slip appears in each one's Print menu (delivery already had it).
Uses _scheduled / _notes so it never AttributeErrors on models without
scheduled_date / notes. Declare the fusion_plating_receiving dep on
reports (already transitive via logistics) for the fp.receiving binding.

Verified on entech: real content for SO-30102, WO-30102, RCV-30103; all
four Print-menu bindings live.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

fusion_plating/fusion_plating_reports/__manifest__.py

@@ -3,7 +3,7 @@
 # License OPL-1 (Odoo Proprietary License v1.0)
 {
     'name': 'Fusion Plating — Reports',
-    'version': '19.0.11.34.0',
+    'version': '19.0.11.36.0',
     'category': 'Manufacturing/Plating',
     'summary': 'PDF reports for Fusion Plating: quote, SO, WO, packing, BoL, CoC, invoice, receipt, quality + compliance.',
     'depends': [
@@ -25,6 +25,11 @@
         # creates a cycle. Our only fp.job touchpoint is wo_scan.py which
         # uses runtime env.get('fp.job') — safe without the manifest dep.
         'fusion_plating_logistics',
+        # Needed for the packing-slip Print binding on fp.receiving
+        # (binding_model_id ref). Already a transitive dep via logistics;
+        # declared explicitly so the ref is robust. No cycle — receiving
+        # does not depend on reports.
+        'fusion_plating_receiving',
     ],
     'data': [
         'security/ir.model.access.csv',