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_configurator/__manifest__.py

@@ -5,7 +5,7 @@
 
 {
     'name': 'Fusion Plating — Configurator',
-    'version': '19.0.17.15.0',
+    'version': '19.0.17.16.0',
     'category': 'Manufacturing/Plating',
     'summary': 'Quotation configurator with part catalog, coating configs, and formula-based pricing engine.',
     'description': """

fusion_plating/fusion_plating_configurator/views/fp_configurator_menu.xml

@@ -15,10 +15,14 @@
         <field name="context">{'default_customer_rank': 1}</field>
     </record>
 
-    <!-- Default landing screen for the Plating app = Sale Orders -->
-    <menuitem id="fusion_plating.menu_fp_root"
-              name="Plating"
-              action="action_fp_sale_orders"/>
+    <!--
+        The Plating app's landing screen is now resolved by a server
+        action defined in fusion_plating core (Phase 1):
+            user.x_fc_plating_landing_action_id  →
+            company.x_fc_default_landing_action_id  →
+            action_fp_sale_orders fallback
+        See fusion_plating/data/fp_landing_data.xml.
+    -->
 
     <!-- ===== SALES submenu under Fusion Plating root ===== -->
     <menuitem id="menu_fp_sales"

fusion_plating/fusion_plating_configurator/views/sale_order_views.xml

@@ -467,6 +467,7 @@
             (0, 0, {'view_mode': 'list', 'view_id': ref('view_sale_order_list_fp_quotes')})]"/>
         <field name="search_view_id" ref="view_sale_order_search_fp_quotes"/>
         <field name="context">{'default_x_fc_delivery_method': 'shipping_partner'}</field>
+        <field name="x_fc_pickable_landing" eval="True"/>
         <field name="help" type="html">
             <p class="o_view_nocontent_smiling_face">
                 Create a new quotation
@@ -482,6 +483,7 @@
         <field name="domain">[('state', 'in', ('sale', 'done'))]</field>
         <field name="view_ids" eval="[(5, 0, 0),
             (0, 0, {'view_mode': 'list', 'view_id': ref('view_sale_order_list_fp')})]"/>
+        <field name="x_fc_pickable_landing" eval="True"/>
     </record>
 
 </odoo>