fix: align Project status enum to Prisma + cascade child records on listing delete

Project status was declared on the frontend as
UPCOMING/SELLING/HANDOVER/COMPLETED but the Prisma enum
ProjectDevelopmentStatus is PLANNING/UNDER_CONSTRUCTION/HANDOVER/
COMPLETED — CREATE failed with "status must be one of …". Aligned the
TypeScript union + PROJECT_STATUS_LABELS/COLORS, filter options on
/projects list, and both new + edit forms. Updated the
normalizeProjectDetail fallback and the du-an test spec to match.

Listings DELETE was blocked by FK references (Inquiry, SavedListing,
PriceHistory, Order, Transaction have no onDelete: Cascade in schema).
Wrapped the Prisma listing delete in a $transaction that removes the
child rows first, then the listing itself, so CRUD from the dashboard
actually lands instead of returning "Referenced record does not exist".

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

apps/web/app/[locale]/(dashboard)/projects/[id]/edit/page.tsx

@@ -31,7 +31,7 @@ const editSchema = z.object({
       'URL không hợp lệ',
     ),
   status: z
-    .enum(['UPCOMING', 'SELLING', 'HANDOVER', 'COMPLETED'])
+    .enum(['PLANNING', 'UNDER_CONSTRUCTION', 'HANDOVER', 'COMPLETED'])
     .optional()
     .or(z.literal('')),
   totalUnits: z
@@ -281,8 +281,8 @@ export default function EditProjectPage() {
             <Label htmlFor="status">Trạng thái</Label>
             <Select id="status" {...register('status')}>
               <option value="">-- Giữ nguyên --</option>
-              <option value="UPCOMING">Sắp mở bán</option>
-              <option value="SELLING">Đang bán</option>
+              <option value="PLANNING">Đang quy hoạch</option>
+              <option value="UNDER_CONSTRUCTION">Đang xây dựng</option>
               <option value="HANDOVER">Đang bàn giao</option>
               <option value="COMPLETED">Đã hoàn thành</option>
             </Select>