feat: Implement comprehensive three-party supply order workflow system

- Added logistics partner selection as mandatory requirement for fulfillment supply orders
- Implemented complete status workflow: PENDING → SUPPLIER_APPROVED → LOGISTICS_CONFIRMED → SHIPPED → DELIVERED
- Created dedicated interfaces for all three parties:
  * Fulfillment: Create orders with mandatory logistics selection and receive shipments
  * Suppliers: View, approve/reject orders, and ship approved orders via /supplies tab
  * Logistics: Confirm/reject transport requests via new /logistics-orders dashboard
- Updated Prisma schema with logisticsPartnerId (non-nullable) and new SupplyOrderStatus enum
- Added comprehensive GraphQL mutations for each party's workflow actions
- Fixed GraphQL resolver to include logistics partners in supplyOrders query
- Enhanced UI components with proper status badges and action buttons
- Added backward compatibility for legacy status handling
- Updated sidebar navigation routing for LOGIST organization type

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

prisma/schema.prisma

@@ -433,6 +433,9 @@ enum SupplyOrderStatus {
   PENDING
   CONFIRMED
   IN_TRANSIT
+  SUPPLIER_APPROVED
+  LOGISTICS_CONFIRMED
+  SHIPPED
   DELIVERED
   CANCELLED
 }