feat(phase1): top-level menu consolidation + landing-page resolver

Phase 1 collapses the Plating app's 17 top-level menus down to 6
domains (Sales, Operations, Receiving & Shipping, Quality,
Compliance, Configuration) so users no longer scroll a 17-item
sidebar to find one thing.

Re-parented (no XML id changes — bookmarks still work):
- fusion_plating_compliance.menu_fp_compliance_root
    → menu_fp_compliance_hub  (renamed 'General')
- fusion_plating_safety.menu_fp_safety_root
    → menu_fp_compliance_hub  (renamed 'Safety / WHMIS')
- fusion_plating_aerospace.menu_fp_aerospace
    → menu_fp_compliance_hub  (renamed 'Aerospace (AS9100 / Nadcap)')
- fusion_plating_nuclear.menu_fp_nuclear
    → menu_fp_compliance_hub  (renamed 'Nuclear (CSA N299 / CNSC)')
- fusion_plating_cgp.menu_fp_cgp
    → menu_fp_compliance_hub  (renamed 'Controlled Goods (CGP)')
- fusion_plating_certificates.menu_fp_certificates
    → menu_fp_quality (Certs are a Quality output, not a separate
      top-level concern)
- fusion_plating_bridge_maintenance.menu_fp_maintenance
    → menu_fp_operations
- fusion_plating.menu_fp_job_step_move (Move Log)
    → menu_fp_operations
- fusion_plating.menu_fp_job_step_timelog (Labor History)
    → menu_fp_operations

The new menu_fp_compliance_hub is supervisor-gated; underlying
verticals retain their own group locks (CGP officer, etc.).

Settings menu remains manager-gated through inheritance from
menu_fp_config (already in place).

NEW — Plating landing-page resolver:
- ir.actions.act_window.x_fc_pickable_landing  (Boolean tag for
  curated picklist; flagged on Sale Orders, Quotations, Process
  Recipes for Phase 1; more in Phase 2)
- res.company.x_fc_default_landing_action_id (admin sets fallback)
- res.users.x_fc_plating_landing_action_id (per-user override)
- ir.actions.server action_fp_resolve_plating_landing — picks
  user → company → Sale Orders fallback at click time
- menu_fp_root rewired to call the resolver
- User profile + Settings tabs surface the dropdowns

Configurator's earlier menu_fp_root override (action_fp_sale_orders
direct) removed — core's resolver now owns the routing.

Versions bumped: fusion_plating 19.0.11.0.0, configurator
19.0.17.16.0, plus 7 dependent modules patched.

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

fusion_plating/fusion_plating/views/fp_menu.xml

@@ -6,13 +6,26 @@
 -->
 <odoo>
 
-    <!-- ===== ROOT APP MENU ===== -->
+    <!-- ===== ROOT APP MENU =====
+         Landing action wired via the resolver server action below.
+         Per-user override > company default > Sale Orders fallback. -->
     <menuitem id="menu_fp_root"
               name="Plating"
               sequence="46"
               web_icon="fusion_plating,static/description/icon.png"
+              action="action_fp_resolve_plating_landing"
               groups="group_fusion_plating_operator"/>
 
+    <!-- ===== Compliance hub (Phase 1) =====
+         Bundles General Compliance + Safety + Aerospace + Nuclear + CGP
+         under one top-level. Each vertical's existing root menu is
+         re-parented here in its own module. -->
+    <menuitem id="menu_fp_compliance_hub"
+              name="Compliance"
+              parent="menu_fp_root"
+              sequence="50"
+              groups="group_fusion_plating_supervisor"/>
+
     <!-- ===== OPERATIONS ===== -->
     <menuitem id="menu_fp_operations"
               name="Operations"