ui(rename): "Plating Job" -> "Work Order" / display "WO # 01368"

Standardise user-facing terminology across 5 modules (27 files):
  - display_name compute: 'Work Order # 01368' -> 'WO # 01368'
  - _description on 5 models: Plating Job{," Step"," Step Time Log"," Margin Report"," Recipe Node Override"} -> Work Order equivalents
  - field labels (string=...) on 13 Many2one / One2many fields
    across fp.batch, fp.thickness_reading, fp.quality.hold,
    fp.job_consumption, fp.portal.job, fp.certificate, fp.delivery,
    fp.quality.check, fp.racking.inspection, res.partner, sale.order
  - XML view labels: action names, list/form/search strings,
    portal template names, dashboard tile titles

What's deliberately preserved:
  - DB model name 'fp.job' (technical identifier — used by
    sale_order.x_fc_plating_job_ids and all comodel refs)
  - Module name 'fusion_plating_jobs' (directory / import path)
  - Settings -> Apps display label 'Fusion Plating Jobs' (module
    identity for Odoo's app picker)
  - 'Use Native Plating Jobs' migration toggle (internal mechanism
    flag, not user-facing terminology)

Verified on entech: WH/JOB/01368 now displays as 'WO # 01368'
everywhere humans look (form header, breadcrumbs, M2O dropdowns,
error messages, smart-button titles).

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

fusion_plating/fusion_plating_quality/__manifest__.py

@@ -5,7 +5,7 @@
 
 {
     'name': 'Fusion Plating — Quality (QMS)',
-    'version': '19.0.4.10.0',
+    'version': '19.0.4.12.2',
     'category': 'Manufacturing/Plating',
     'summary': 'Native QMS for plating shops: NCR, CAPA, calibration, AVL, FAIR, '
                'internal audits, customer specs, document control. CE + EE compatible.',
@@ -96,6 +96,7 @@ Copyright (c) 2026 Nexa Systems Inc. All rights reserved.
         'views/res_partner_views.xml',
         'views/res_partner_qc_views.xml',
         'views/res_config_settings_views.xml',
+        'wizards/fp_contract_review_client_email_wizard_views.xml',
         'views/fp_contract_review_views.xml',
         'views/fp_part_catalog_views.xml',
         'views/fp_quality_check_views.xml',

fusion_plating/fusion_plating_quality/models/fp_quality_check.py

@@ -42,7 +42,7 @@ class FpQualityCheck(models.Model):
         default=lambda self: self._default_name(), tracking=True,
     )
     job_id = fields.Many2one(
-        'fp.job', string='Plating Job',
+        'fp.job', string='Work Order',
         required=True, ondelete='cascade', tracking=True,
         index=True,
     )

fusion_plating/fusion_plating_quality/models/fp_quality_hold.py

@@ -35,7 +35,7 @@ class FpQualityHold(models.Model):
     # The bridge fields stay during the migration window so existing
     # records keep their FKs; Phase 5 removes bridge_mrp entirely.
     job_id = fields.Many2one(
-        'fp.job', string='Plating Job',
+        'fp.job', string='Work Order',
         index=True, ondelete='set null',
     )
     step_id = fields.Many2one(