feat(freight-backoffice): render reports from the server-driven catalog

Drop reportConfigs.ts (per-report FE config duplicating the backend) and
the chart-drawing ReportPage. Replace with ReportView: one engine that
renders any report the GET /reports catalog describes — filters, KPI
strip, sortable/paginated DataTable, xlsx/pdf export via blob download.
ReportSection embeds a report inline on any page, scoped by idKey, and
renders nothing if the caller lacks that report's permission.

Sidebar Reports submenu is now built from the live catalog
(sidebar-sections.tsx + App.tsx) instead of a hand-listed key — no FE
edit needed to add or hide a report.

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

@@ -174,7 +174,7 @@ import {
 } from "./locomotives.service";
 import { overviewService } from "./overview.service";
 import { reportsService } from "./reports.service";
-import type { ReportQueryInput, ReportResult } from "@/types/reports";
+import type { ReportCatalogEntry, ReportRunParams, ReportRunResult } from "@/types/reports";
 import {
   paymentsService,
   type PaginatedPayments,
@@ -3030,7 +3030,10 @@ export const api = {
   },
 
   reports: {
-    run: endpoint<ReportQueryInput, ReportResult>(
+    catalog: endpoint<void, ReportCatalogEntry[]>("reports", "catalog", () =>
+      reportsService.catalog(),
+    ),
+    run: endpoint<ReportRunParams, ReportRunResult>(
       "reports",
       "run",
       (input) => reportsService.run(input),