refactor: rename Wizamart to Orion across entire codebase

Replace all ~1,086 occurrences of Wizamart/wizamart/WIZAMART/WizaMart
with Orion/orion/ORION across 184 files. This includes database
identifiers, email addresses, domain references, R2 bucket names,
DNS prefixes, encryption salt, Celery app name, config defaults,
Docker configs, CI configs, documentation, seed data, and templates.

Renames homepage-wizamart.html template to homepage-orion.html.
Fixes duplicate file_pattern key in api.yaml architecture rule.

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

docs/development/error-rendering/error-rendering-developer-documentation.md

@@ -182,7 +182,7 @@ ErrorPageRenderer.render_error_page(
 
 **Handlers:**
 
-- `WizamartException` - Custom application exceptions
+- `OrionException` - Custom application exceptions
 - `HTTPException` - FastAPI HTTP exceptions
 - `RequestValidationError` - Pydantic validation errors
 - `Exception` - Generic Python exceptions

docs/development/error-rendering/html-error-rendering-flow-diagram.md

@@ -41,7 +41,7 @@
                                              ▼
             ┌────────────────────────────────────────────────────────┐
             │              Exception Handler                         │
-            │  - WizamartException                                   │
+            │  - OrionException                                   │
             │  - HTTPException                                       │
             │  - RequestValidationError                             │
             │  - Generic Exception                                   │
@@ -296,14 +296,14 @@ middleware/
 
 ## Benefits Summary
 
-✅ **Separation of Concerns**: HTML templates separate from handler logic  
-✅ **Context-Aware**: Different error pages for different areas  
-✅ **Maintainable**: Easy to update individual error pages  
-✅ **Scalable**: Easy to add new contexts or error types  
-✅ **Professional**: Polished error pages matching area design  
-✅ **Flexible**: Fallback mechanism ensures errors always render  
-✅ **Secure**: Debug info only shown to admins  
-✅ **Themed**: Shop errors can use store branding (Phase 3)  
+✅ **Separation of Concerns**: HTML templates separate from handler logic
+✅ **Context-Aware**: Different error pages for different areas
+✅ **Maintainable**: Easy to update individual error pages
+✅ **Scalable**: Easy to add new contexts or error types
+✅ **Professional**: Polished error pages matching area design
+✅ **Flexible**: Fallback mechanism ensures errors always render
+✅ **Secure**: Debug info only shown to admins
+✅ **Themed**: Shop errors can use store branding (Phase 3)
 
 ---