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/parks/models/companies.py

@@ -2,6 +2,7 @@ from django.contrib.postgres.fields import ArrayField
 from django.db import models
 from django.utils.text import slugify
 from apps.core.models import TrackedModel
+from apps.core.choices.fields import RichChoiceField
 import pghistory
 
 
@@ -12,14 +13,10 @@ class Company(TrackedModel):
 
     objects = CompanyManager()
 
-    class CompanyRole(models.TextChoices):
-        OPERATOR = "OPERATOR", "Park Operator"
-        PROPERTY_OWNER = "PROPERTY_OWNER", "Property Owner"
-
     name = models.CharField(max_length=255)
     slug = models.SlugField(max_length=255, unique=True)
     roles = ArrayField(
-        models.CharField(max_length=20, choices=CompanyRole.choices),
+        RichChoiceField(choice_group="company_roles", domain="parks", max_length=20),
         default=list,
         blank=True,
     )