feat: complete modular platform architecture (Phases 1-5)

Phase 1 - Vendor Router Integration:
- Wire up vendor module routers in app/api/v1/vendor/__init__.py
- Use lazy imports via __getattr__ to avoid circular dependencies

Phase 2 - Extract Remaining Modules:
- Create 6 new module directories: customers, cms, analytics, messaging,
  dev_tools, monitoring
- Each module has definition.py and route wrappers
- Update registry to import from extracted modules

Phase 3 - Database Table Migration:
- Add PlatformModule junction table for auditable module tracking
- Add migration zc2m3n4o5p6q7_add_platform_modules_table.py
- Add modules relationship to Platform model
- Update ModuleService with JSON-to-junction-table migration

Phase 4 - Module-Specific Configuration UI:
- Add /api/v1/admin/module-config/* endpoints
- Add module-config.html template and JS

Phase 5 - Integration Tests:
- Add tests/fixtures/module_fixtures.py
- Add tests/integration/api/v1/admin/test_modules.py
- Add tests/integration/api/v1/modules/test_module_access.py

Architecture fixes:
- Fix JS-003 errors: use ...data() directly in Alpine components
- Fix JS-005 warnings: add init() guards to prevent duplicate init
- Fix API-001 errors: add MenuActionResponse Pydantic model
- Add FE-008 noqa for dynamic number input in template

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

app/modules/cms/__init__.py

@@ -0,0 +1,22 @@
+# app/modules/cms/__init__.py
+"""
+CMS Module - Content Management System.
+
+This module provides:
+- Content pages management
+- Media library
+- Vendor themes
+- SEO tools
+
+Routes:
+- Admin: /api/v1/admin/content-pages/*
+- Vendor: /api/v1/vendor/content-pages/*, /api/v1/vendor/media/*
+
+Menu Items:
+- Admin: content-pages, vendor-themes
+- Vendor: content-pages, media
+"""
+
+from app.modules.cms.definition import cms_module
+
+__all__ = ["cms_module"]