feat(reports): record loading and unloading time per stop

The OCC report publishes total loading and unloading time and the other
activity left over from a station stay, but nothing recorded when handling
started or ended — the July 2026 seed had to write the figure into a
checkpoint note. Four nullable stamps now ride the stop's arrival row, which
is the row the staying-time report builds a stay from (a turnaround's
departure belongs to a different schedule).

Handling is unloading start to loading end, so a container stop reads as one
window and a bulk station that only loads or only unloads still reports its
half; other activity is the rest of the stay. Both stay NULL where nothing
was logged rather than collapsing to zero.

- station-staying-time: + loading/unloading and other activity per stop
- turnaround-cycle: + the same, summed over the cycle's stops
- loading-unloading (new): per train per station per period, so a week or
  month view is that train's average over its stops
- the stop/stay query moves to operations-classification, shared by both

apps/edr-freight-api/src/modules/reports/report.registry.ts

@@ -34,6 +34,7 @@ import { cargoVolumePerformanceReport } from "./definitions/cargo-volume-perform
 import { chargedVsActualVolumeReport } from "./definitions/charged-vs-actual-volume.report";
 import { cargoVolumeByStationReport } from "./definitions/cargo-volume-by-station.report";
 import { portWarehouseSummaryReport } from "./definitions/port-warehouse-summary.report";
+import { loadingUnloadingReport } from "./definitions/loading-unloading.report";
 import { ReportDefinition } from "./report.types";
 
 /**
@@ -77,6 +78,7 @@ export const REPORTS: ReportDefinition[] = [
   chargedVsActualVolumeReport,
   cargoVolumeByStationReport,
   portWarehouseSummaryReport,
+  loadingUnloadingReport,
 ];
 
 const BY_KEY = new Map<ReportKey, ReportDefinition>(