feat(plating-menu): Layer 1+2 — explicit groups on top-level menus + submenus

Phase D Tasks D1-D4 of permissions overhaul. Adds explicit groups=
attributes to:
- 9 top-level Plating menus (matrix per spec Section 2.E)
- Quality submenus: Audits, Customer Specs, AVL → QM-only
- Compliance hub child submenus (CGP, General, Safety, Aerospace,
  Nuclear) → QM-only
- Operations submenus: Maintenance, Move Log, Labor History → Shop
  Manager+; Replenishment Suggestions → Manager+

Replaces fragile inheritance + action-ACL-based visibility with
explicit per-menu gates. Now every role's menu tree is deterministic.

Also adds fusion_plating/tests/test_menu_visibility.py — per-role
matrix tests using ir.ui.menu.search_count with the test user.

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

fusion_plating/fusion_plating_bridge_maintenance/__manifest__.py

@@ -4,7 +4,7 @@
 
 {
     'name': 'Fusion Plating — Maintenance Bridge',
-    'version': '19.0.1.2.1',
+    'version': '19.0.1.2.2',
     'category': 'Manufacturing/Plating',
     'summary': 'Bridge standard Odoo Maintenance with Fusion Plating equipment, '
                'plans, checklists, and sensor integration.',

fusion_plating/fusion_plating_bridge_maintenance/views/fp_maintenance_menu.xml

@@ -3,11 +3,13 @@
 
     <!-- Phase 1 — re-parented under Plating → Operations. Maintenance
          is an Operations concern, not a separate top-level. -->
+    <!-- Phase D (perms v2) — Shop Manager+ only. Operators don't need
+         to schedule plans or browse the equipment registry. -->
     <menuitem id="menu_fp_maintenance"
               name="Maintenance"
               parent="fusion_plating.menu_fp_operations"
               sequence="80"
-              groups="fusion_plating.group_fusion_plating_operator"/>
+              groups="fusion_plating.group_fp_shop_manager_v2"/>
 
     <menuitem id="menu_fp_maintenance_active"
               name="Active Events"