Add comprehensive API documentation for ThrillWiki integration and features

- Introduced Next.js integration guide for ThrillWiki API, detailing authentication, core domain APIs, data structures, and implementation patterns.
- Documented the migration to Rich Choice Objects, highlighting changes for frontend developers and enhanced metadata availability.
- Fixed the missing `get_by_slug` method in the Ride model, ensuring proper functionality of ride detail endpoints.
- Created a test script to verify manufacturer syncing with ride models, ensuring data integrity across related models.

backend/apps/rides/models/media.py

@@ -8,6 +8,7 @@ from typing import Any, Optional, List, cast
 from django.db import models
 from django.conf import settings
 from apps.core.history import TrackedModel
+from apps.core.choices import RichChoiceField
 from apps.core.services.media_service import MediaService
 import pghistory
 
@@ -48,17 +49,12 @@ class RidePhoto(TrackedModel):
     is_approved = models.BooleanField(default=False)
 
     # Ride-specific metadata
-    photo_type = models.CharField(
+    photo_type = RichChoiceField(
+        choice_group="photo_types",
+        domain="rides",
         max_length=50,
-        choices=[
-            ("exterior", "Exterior View"),
-            ("queue", "Queue Area"),
-            ("station", "Station"),
-            ("onride", "On-Ride"),
-            ("construction", "Construction"),
-            ("other", "Other"),
-        ],
         default="exterior",
+        help_text="Type of photo for categorization and display purposes"
     )
 
     # Metadata