enhancement: Support Dual-Layer Navigation Structure Using Modules and ModuleHasNavigations #33

Summary

Refactor navigation loading to support two distinct navigation layers:

1. Module Navigation

   • Hardcoded module-level entries
   • Examples: User Interface, User Management, Foundation
   • Controls top-level module selection and ordering

2. Sidebar Navigation

   • Loaded dynamically using ModuleHasNavigations
   • Controls forms, tables, entities, and other module-specific sidebar items

Problem

The current navigation implementation does not clearly separate module navigation from sidebar navigation, making it difficult to manage ordering, labels, icons, and module-specific sidebar content independently.

Scope

• Introduce separate handling for module navigation and sidebar navigation
• Keep module navigation as the source of top-level modules
• Load sidebar items from ModuleHasNavigations
• Support module-specific navigation rendering
• Ensure navigation data can be extended for future Navigation UI editor support
• Maintain compatibility with existing sidebar rendering

Acceptance Criteria

• Top-level modules are rendered independently of sidebar items
• Sidebar items are loaded through ModuleHasNavigations
• Module ordering, labels, and icons can be managed separately
• Existing module navigation continues to function
• Foundation navigation structure supports future Navigation editor requirements