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

@@ -65,25 +65,25 @@ urlpatterns = [
     ),
     # Park-specific category URLs
     path(
-        "<slug:park_slug>/roller_coasters/",
+        "<slug:park_slug>/roller-coasters/",
         ParkSingleCategoryListView.as_view(),
         {"category": "RC"},
         name="park_roller_coasters",
     ),
     path(
-        "<slug:park_slug>/dark_rides/",
+        "<slug:park_slug>/dark-rides/",
         ParkSingleCategoryListView.as_view(),
         {"category": "DR"},
         name="park_dark_rides",
     ),
     path(
-        "<slug:park_slug>/flat_rides/",
+        "<slug:park_slug>/flat-rides/",
         ParkSingleCategoryListView.as_view(),
         {"category": "FR"},
         name="park_flat_rides",
     ),
     path(
-        "<slug:park_slug>/water_rides/",
+        "<slug:park_slug>/water-rides/",
         ParkSingleCategoryListView.as_view(),
         {"category": "WR"},
         name="park_water_rides",