feat(listings): phase C — nearby POIs on listing detail map

Backend
-------
- New endpoint GET /analytics/pois/nearby?lat&lng&radius&limit (public,
  no guard). Mirrors the neighborhoods/:district/score shape.
- Prisma $queryRawUnsafe with PostGIS ST_DWithin on POI.location::geography
  and ST_Distance for the ordered-by-distance result. Default radius 2km,
  max 10km; default limit 30, max 100.
- Response maps POIType enum → frontend POICategory so the existing pill
  filter in NeighborhoodPOIMap works out of the box:
    SCHOOL/UNIVERSITY → school
    HOSPITAL/CLINIC/PHARMACY → hospital
    METRO_STATION/BUS_STOP → transit
    MALL/MARKET/SUPERMARKET/BANK/ATM → shopping
    RESTAURANT/CAFE → restaurant
    PARK → park
    else → shopping (fallback, still filterable)
- New files: application/queries/get-nearby-pois/{query,handler}.ts +
  presentation/dto/get-nearby-pois.dto.ts. Registered in analytics.module.ts.

Frontend
--------
- analytics-api.ts: exports NearbyPOI, NearbyPOIsResponse, NearbyPOICategory
  and analyticsApi.getNearbyPOIs(lat, lng, radius?, limit?).
- listing-detail-client.tsx: the "Vị trí trên bản đồ" card no longer
  renders <ListingMap> for a single pin — it now renders
  <NeighborhoodPOIMap> with the property's coords as center, the nearby
  POIs as markers, and the existing category-filter pills. A small
  "Tìm thấy N điểm quan tâm trong bán kính 2 km" summary sits below.
- The neighborhood score radar card remains below, untouched.
- The spec fixture + mocks extended for the new analyticsApi dependency.

No schema change, no migration. Phase C of 4.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

apps/web/lib/analytics-api.ts

@@ -67,6 +67,30 @@ export interface DistrictStatsResponse {
   districts: DistrictStats[];
 }
 
+export type NearbyPOICategory =
+  | 'school'
+  | 'hospital'
+  | 'transit'
+  | 'shopping'
+  | 'restaurant'
+  | 'park';
+
+export interface NearbyPOI {
+  id: string;
+  name: string;
+  type: string;
+  category: NearbyPOICategory;
+  lat: number;
+  lng: number;
+  distance: number;
+  address: string | null;
+}
+
+export interface NearbyPOIsResponse {
+  pois: NearbyPOI[];
+  center: { lat: number; lng: number };
+}
+
 export const analyticsApi = {
   getMarketReport: (city: string, period: string, propertyType?: string) => {
     const params = new URLSearchParams({ city, period });
@@ -88,4 +112,9 @@ export const analyticsApi = {
     const params = new URLSearchParams({ city, period });
     return apiClient.get<DistrictStatsResponse>(`/analytics/district-stats?${params}`);
   },
+
+  getNearbyPOIs: (lat: number, lng: number, radius = 2000, limit = 30) =>
+    apiClient.get<NearbyPOIsResponse>(
+      `/analytics/pois/nearby?lat=${lat}&lng=${lng}&radius=${radius}&limit=${limit}`,
+    ),
 };