Rename Adventures to Locations (#696)

* Refactor user_id to user in adventures and related models, views, and components

- Updated all instances of user_id to user in the adventures app, including models, serializers, views, and frontend components.
- Adjusted queries and filters to reflect the new user field naming convention.
- Ensured consistency across the codebase for user identification in adventures, collections, notes, and transportation entities.
- Modified frontend components to align with the updated data structure, ensuring proper access control and rendering based on user ownership.

* Refactor adventure-related views and components to use "Location" terminology

- Updated GlobalSearchView to replace AdventureSerializer with LocationSerializer.
- Modified IcsCalendarGeneratorViewSet to use LocationSerializer instead of AdventureSerializer.
- Created new LocationImageViewSet for managing location images, including primary image toggling and image deletion.
- Introduced LocationViewSet for managing locations with enhanced filtering, sorting, and sharing capabilities.
- Updated ReverseGeocodeViewSet to utilize LocationSerializer.
- Added ActivityTypesView to retrieve distinct activity types from locations.
- Refactored user views to replace AdventureSerializer with LocationSerializer.
- Updated frontend components to reflect changes from "adventure" to "location", including AdventureCard, AdventureLink, AdventureModal, and others.
- Adjusted API endpoints in frontend routes to align with new location-based structure.
- Ensured all references to adventures are replaced with locations across the codebase.

* refactor: rename adventures to locations across the application

- Updated localization files to replace adventure-related terms with location-related terms.
- Refactored TypeScript types and variables from Adventure to Location in various routes and components.
- Adjusted UI elements and labels to reflect the change from adventures to locations.
- Ensured all references to adventures in the codebase are consistent with the new location terminology.

* Refactor code structure for improved readability and maintainability

* feat: Implement location details page with server-side loading and deletion functionality

- Added +page.server.ts to handle server-side loading of additional location info.
- Created +page.svelte for displaying location details, including images, visits, and maps.
- Integrated GPX file handling and rendering on the map.
- Updated map route to link to locations instead of adventures.
- Refactored profile and search routes to use LocationCard instead of AdventureCard.

* docs: Update terminology from "Adventure" to "Location" and enhance project overview

* docs: Clarify collection examples in usage documentation

* feat: Enable credentials for GPX file fetch and add CORS_ALLOW_CREDENTIALS setting

* Refactor adventure references to locations across the backend and frontend

- Updated CategoryViewSet to reflect location context instead of adventures.
- Modified ChecklistViewSet to include locations in retrieval logic.
- Changed GlobalSearchView to search for locations instead of adventures.
- Adjusted IcsCalendarGeneratorViewSet to handle locations instead of adventures.
- Refactored LocationImageViewSet to remove unused import.
- Updated LocationViewSet to clarify public access for locations.
- Changed LodgingViewSet to reference locations instead of adventures.
- Modified NoteViewSet to prevent listing all locations.
- Updated RecommendationsViewSet to handle locations in parsing and response.
- Adjusted ReverseGeocodeViewSet to search through user locations.
- Updated StatsViewSet to count locations instead of adventures.
- Changed TagsView to reflect activity types for locations.
- Updated TransportationViewSet to reference locations instead of adventures.
- Added new translations for search results related to locations in multiple languages.
- Updated dashboard and profile pages to reflect location counts instead of adventure counts.
- Adjusted search routes to handle locations instead of adventures.

* Update banner image

* style: Update stats component background and border for improved visibility

* refactor: Rename AdventureCard and AdventureModal to LocationCard and LocationModal for consistency

backend/server/adventures/views/recommendations_view.py

@@ -5,8 +5,6 @@ from rest_framework.response import Response
 from django.conf import settings
 import requests
 from geopy.distance import geodesic
-import time
-
 
 class RecommendationsViewSet(viewsets.ViewSet):
     permission_classes = [IsAuthenticated]
@@ -14,7 +12,7 @@ class RecommendationsViewSet(viewsets.ViewSet):
     HEADERS = {'User-Agent': 'AdventureLog Server'}
 
     def parse_google_places(self, places, origin):
-        adventures = []
+        locations = []
 
         for place in places:
             location = place.get('location', {})
@@ -45,16 +43,16 @@ class RecommendationsViewSet(viewsets.ViewSet):
                 "distance_km": round(distance_km, 2),
             }
 
-            adventures.append(adventure)
+            locations.append(adventure)
 
         # Sort by distance ascending
-        adventures.sort(key=lambda x: x["distance_km"])
+        locations.sort(key=lambda x: x["distance_km"])
 
-        return adventures
+        return locations
     
     def parse_overpass_response(self, data, request):
         nodes = data.get('elements', [])
-        adventures = []
+        locations = []
         all = request.query_params.get('all', False)
 
         origin = None
@@ -102,13 +100,13 @@ class RecommendationsViewSet(viewsets.ViewSet):
                 "powered_by": "osm"
             }
 
-            adventures.append(adventure)
+            locations.append(adventure)
 
         # Sort by distance if available
         if origin:
-            adventures.sort(key=lambda x: x.get("distance_km") or float("inf"))
+            locations.sort(key=lambda x: x.get("distance_km") or float("inf"))
 
-        return adventures
+        return locations
 
     
     def query_overpass(self, lat, lon, radius, category, request):
@@ -172,8 +170,8 @@ class RecommendationsViewSet(viewsets.ViewSet):
             print("Overpass API error:", e)
             return Response({"error": "Failed to retrieve data from Overpass API."}, status=500)
 
-        adventures = self.parse_overpass_response(data, request)
-        return Response(adventures)
+        locations = self.parse_overpass_response(data, request)
+        return Response(locations)
 
     def query_google_nearby(self, lat, lon, radius, category, request):
         """Query Google Places API (New) for nearby places"""
@@ -216,9 +214,9 @@ class RecommendationsViewSet(viewsets.ViewSet):
             
             places = data.get('places', [])
             origin = (float(lat), float(lon))
-            adventures = self.parse_google_places(places, origin)
+            locations = self.parse_google_places(places, origin)
             
-            return Response(adventures)
+            return Response(locations)
             
         except requests.exceptions.RequestException as e:
             print(f"Google Places API error: {e}")