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/api/v1/serializers/parks.py

@@ -15,6 +15,7 @@ from config.django import base as settings
 
 from .shared import LocationOutputSerializer, CompanyOutputSerializer, ModelChoices
 from apps.core.services.media_url_service import MediaURLService
+from apps.core.choices.serializers import RichChoiceFieldSerializer
 
 
 # === PARK SERIALIZERS ===
@@ -51,7 +52,10 @@ class ParkListOutputSerializer(serializers.Serializer):
     id = serializers.IntegerField()
     name = serializers.CharField()
     slug = serializers.CharField()
-    status = serializers.CharField()
+    status = RichChoiceFieldSerializer(
+        choice_group="statuses",
+        domain="parks"
+    )
     description = serializers.CharField()
 
     # Statistics
@@ -141,7 +145,10 @@ class ParkDetailOutputSerializer(serializers.Serializer):
     id = serializers.IntegerField()
     name = serializers.CharField()
     slug = serializers.CharField()
-    status = serializers.CharField()
+    status = RichChoiceFieldSerializer(
+        choice_group="statuses",
+        domain="parks"
+    )
     description = serializers.CharField()
 
     # Details