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/search.py

@@ -6,6 +6,8 @@ and other search functionality.
 """
 
 from rest_framework import serializers
+from ..shared import ModelChoices
+from apps.core.choices.serializers import RichChoiceFieldSerializer
 
 
 # === CORE ENTITY SEARCH SERIALIZERS ===
@@ -16,7 +18,9 @@ class EntitySearchInputSerializer(serializers.Serializer):
 
     query = serializers.CharField(max_length=255, help_text="Search query string")
     entity_types = serializers.ListField(
-        child=serializers.ChoiceField(choices=["park", "ride", "company", "user"]),
+        child=serializers.ChoiceField(
+            choices=ModelChoices.get_entity_type_choices()
+        ),
         required=False,
         help_text="Types of entities to search for",
     )
@@ -34,7 +38,10 @@ class EntitySearchResultSerializer(serializers.Serializer):
     id = serializers.IntegerField()
     name = serializers.CharField()
     slug = serializers.CharField()
-    type = serializers.CharField()
+    type = RichChoiceFieldSerializer(
+        choice_group="entity_types",
+        domain="core"
+    )
     description = serializers.CharField()
     relevance_score = serializers.FloatField()