add yard distances management to rule engine

- Introduced new yard distances resource with CRUD operations.
- Created migration for yard distances table with necessary constraints.
- Implemented service and repository for yard distances handling.
- Added controller for API endpoints to manage yard distances.
- Updated rule engine configuration to include yard distances.
- Enhanced rule engine resource page to support yard distance selection.
- Updated contracts and train builder pages to handle new yard distance logic.
- Added error handling utility for better error message extraction.

apps/edr-freight-web/backoffice/src/auth/http.ts

@@ -115,13 +115,16 @@ api.interceptors.response.use(
       // Surface the server's actual error message in the global error modal
       // (401s are handled by the session-refresh flow, so skip them). A request
       // may opt out via `suppressErrorModal` when it handles the failure itself.
-      if (
-        error.response &&
-        error.response.status !== 401 &&
-        !originalRequest?.suppressErrorModal
-      ) {
+      if (error.response && error.response.status !== 401) {
         const payload = extractApiErrorPayload(error);
-        if (payload) emitApiError(payload);
+        // Normalize the error's own `message` to the SERVER's actual message so
+        // every downstream `toast.error(err.message)` / MutationCache handler
+        // shows the real cause instead of "Request failed with status code NNN".
+        // Applies even on suppressErrorModal paths — only the modal is opted out.
+        if (payload?.messages.length) {
+          (error as { message?: string }).message = payload.messages.join("\n");
+        }
+        if (payload && !originalRequest?.suppressErrorModal) emitApiError(payload);
       }
       return Promise.reject(error);
     }