feat: add hazardous goods declaration feature

- Introduced HazardDeclarationPanel component to display dangerous goods declaration details.
- Updated URL constants to include CLEARANCE_PROCEED endpoint for re-requesting operations.
- Enhanced permissions to include hazardous approval roles for contract approvals.
- Integrated HazardDeclarationPanel into ContractRequestDetailPage and ContractClearanceDetailPage.
- Added proceedToOperation method in bookings service for handling operation re-requests.
- Updated contract forms and schemas to include hazard class and UN number fields.
- Implemented validation for hazardous contracts in the contract creation flow.
- Added expiry notice functionality for contracts nearing validity end.
- Created tests for expiry notice calculations and labels.
- Updated UI components to reflect hazardous cargo information and validation errors.

apps/edr-freight-web/backoffice/src/services/api.ts

@@ -2533,6 +2533,13 @@ export const api = {
       bookingsService.reviewOperation(id, decision, { note }),
     ),
 
+    proceedToOperation: endpoint<
+      { id: string; scheduledDate: string },
+      BookingDetail
+    >("bookings", "proceedToOperation", ({ id, scheduledDate }) =>
+      bookingsService.proceedToOperation(id, scheduledDate),
+    ),
+
     generateContract: endpoint<{ id: string }, BookingDetail>(
       "bookings",
       "generateContract",

apps/edr-freight-web/backoffice/src/services/bookings.service.ts

@@ -243,6 +243,14 @@ export const bookingsService = {
       ...options,
     }),
 
+  /**
+   * Re-request operation on a booking Operations sent back for changes. The
+   * customer path uses the same endpoint from the portal; GL needs it here
+   * because a customs booking is GL's to fix, not the customer's.
+   */
+  proceedToOperation: (id: string, scheduledDate: string) =>
+    postBooking<BookingDetail>(B.CLEARANCE_PROCEED(id), { scheduledDate }),
+
   generateContract: (id: string) =>
     postBooking<BookingDetail>(B.CONTRACT_GENERATE(id)),