feat(eims): resolve buyer geography from the MoR location master

BuyerDetails Country/Region/City/Wereda now resolve from the Ministry's own
EIMS_COUNTRY_REGION_VW master instead of the EIMS_BUYER_*_CODES env maps and
the ethiopia-geo-codes table. Both invented their codes and looked names up
globally, so KERSA/GORO/BABILE/BURE — each present in several zones with
different LOCALITY_NOs — could be filed against the wrong jurisdiction.

Resolution is hierarchical and refuses to guess: an unknown or ambiguous
address raises a local validation error naming the level that failed, and
never selects the first matching row. Spelling differences between EDR and
MoR live in a reviewed, parent-scoped alias layer; the dataset itself stays
verbatim so it remains traceable to the Ministry sheet.

Resolution now runs before the counter reservation in both the single and
bulk paths, so a bad company address no longer burns an EIMS sequence number.

Adds eims:import-locations to regenerate the dataset from a future workbook,
reporting duplicate rows and same-hierarchy code conflicts.

apps/edr-freight-web/backoffice/src/constants/URLS.ts

@@ -780,6 +780,8 @@ export const URL_CONSTANTS = {
       `/import-operations/empty-container-returns/${id}/status`,
     EMPTY_CONTAINER_RETURNS_LOAD_ON_TRAIN:
       "/import-operations/empty-container-returns/load-on-train",
+    EMPTY_CONTAINER_RETURN_DOCUMENT: (id: string) =>
+      `/import-operations/empty-container-returns/${id}/document`,
   },
 
   VEHICLES: {