refactor: complete module-driven architecture migration

This commit completes the migration to a fully module-driven architecture:

## Models Migration
- Moved all domain models from models/database/ to their respective modules:
  - tenancy: User, Admin, Vendor, Company, Platform, VendorDomain, etc.
  - cms: MediaFile, VendorTheme
  - messaging: Email, VendorEmailSettings, VendorEmailTemplate
  - core: AdminMenuConfig
- models/database/ now only contains Base and TimestampMixin (infrastructure)

## Schemas Migration
- Moved all domain schemas from models/schema/ to their respective modules:
  - tenancy: company, vendor, admin, team, vendor_domain
  - cms: media, image, vendor_theme
  - messaging: email
- models/schema/ now only contains base.py and auth.py (infrastructure)

## Routes Migration
- Moved admin routes from app/api/v1/admin/ to modules:
  - menu_config.py -> core module
  - modules.py -> tenancy module
  - module_config.py -> tenancy module
- app/api/v1/admin/ now only aggregates auto-discovered module routes

## Menu System
- Implemented module-driven menu system with MenuDiscoveryService
- Extended FrontendType enum: PLATFORM, ADMIN, VENDOR, STOREFRONT
- Added MenuItemDefinition and MenuSectionDefinition dataclasses
- Each module now defines its own menu items in definition.py
- MenuService integrates with MenuDiscoveryService for template rendering

## Documentation
- Updated docs/architecture/models-structure.md
- Updated docs/architecture/menu-management.md
- Updated architecture validation rules for new exceptions

## Architecture Validation
- Updated MOD-019 rule to allow base.py in models/schema/
- Created core module exceptions.py and schemas/ directory
- All validation errors resolved (only warnings remain)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

app/modules/customers/static/admin/js/customers.js

@@ -101,6 +101,9 @@ function adminCustomers() {
         },
 
         async init() {
+            // Load i18n translations
+            await I18n.loadModule('customers');
+
             customersLog.debug('Customers page initialized');
 
             // Load platform settings for rows per page
@@ -369,7 +372,7 @@ function adminCustomers() {
                 customersLog.info(response.message);
             } catch (error) {
                 customersLog.error('Failed to toggle status:', error);
-                Utils.showToast(error.message || 'Failed to toggle customer status', 'error');
+                Utils.showToast(error.message || I18n.t('customers.messages.failed_to_toggle_customer_status'), 'error');
             }
         },
 

app/modules/customers/static/vendor/js/customers.js

@@ -97,6 +97,9 @@ function vendorCustomers() {
         },
 
         async init() {
+            // Load i18n translations
+            await I18n.loadModule('customers');
+
             vendorCustomersLog.info('Customers init() called');
 
             // Guard against multiple initialization
@@ -218,7 +221,7 @@ function vendorCustomers() {
                 vendorCustomersLog.info('Loaded customer details:', customer.id);
             } catch (error) {
                 vendorCustomersLog.error('Failed to load customer details:', error);
-                Utils.showToast(error.message || 'Failed to load customer details', 'error');
+                Utils.showToast(error.message || I18n.t('customers.messages.failed_to_load_customer_details'), 'error');
             } finally {
                 this.loading = false;
             }
@@ -237,7 +240,7 @@ function vendorCustomers() {
                 vendorCustomersLog.info('Loaded customer orders:', customer.id, this.customerOrders.length);
             } catch (error) {
                 vendorCustomersLog.error('Failed to load customer orders:', error);
-                Utils.showToast(error.message || 'Failed to load customer orders', 'error');
+                Utils.showToast(error.message || I18n.t('customers.messages.failed_to_load_customer_orders'), 'error');
             } finally {
                 this.loading = false;
             }