fix(fusion_plating_jobs): restore quick_look_partner_id + quick_look_part_catalog_id

Commit b0070afc removed these two related fields from fp.job.step but
the view fp_job_step_quick_look_views.xml still references them. The
mismatch was dormant because entech never ran -u between b0070afc
and the 2026-05-22 deploy. Re-running -u during the Phase 1-4 deploy
caught it:

  Field "quick_look_part_catalog_id" does not exist in model
  "fp.job.step"

Restoring both as related fields (zero-cost, fixes the view without
touching XML).

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

fusion_plating/fusion_plating_jobs/models/fp_job_step.py

@@ -1200,6 +1200,22 @@ class FpJobStep(models.Model):
     # quick-look modal. The modal is bound via context= on the parent
     # job form's <field name="step_ids"/> — no TransientModel needed.
 
+    # Job-level context for the quick-look modal — restored after commit
+    # b0070afc accidentally removed these while still referencing them in
+    # fp_job_step_quick_look_views.xml (entech caught the mismatch during
+    # the 2026-05-22 Phase 1-4 deploy).
+    quick_look_partner_id = fields.Many2one(
+        'res.partner',
+        string='Customer',
+        related='job_id.partner_id',
+        readonly=True,
+    )
+    quick_look_part_catalog_id = fields.Many2one(
+        'fp.part.catalog',
+        string='Part',
+        related='job_id.part_catalog_id',
+        readonly=True,
+    )
     quick_look_instructions = fields.Html(
         string='Operator Instructions',
         related='recipe_node_id.description',