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

@@ -8,25 +8,25 @@ urlpatterns = [
     path("", views.RideListView.as_view(), name="global_ride_list"),
     # Global category views
     path(
-        "roller_coasters/",
+        "roller-coasters/",
         views.SingleCategoryListView.as_view(),
         {"category": "RC"},
         name="global_roller_coasters",
     ),
     path(
-        "dark_rides/",
+        "dark-rides/",
         views.SingleCategoryListView.as_view(),
         {"category": "DR"},
         name="global_dark_rides",
     ),
     path(
-        "flat_rides/",
+        "flat-rides/",
         views.SingleCategoryListView.as_view(),
         {"category": "FR"},
         name="global_flat_rides",
     ),
     path(
-        "water_rides/",
+        "water-rides/",
         views.SingleCategoryListView.as_view(),
         {"category": "WR"},
         name="global_water_rides",