fix(maps): ask Amap only where Amap can answer

With Amap in the keyed slot every reverse lookup went to Amap first,
worldwide. Outside its box that buys a round trip and an empty answer
before Nominatim is asked anyway, which is latency on every right click in
Lisbon. The client side of the same question already filters by the box
(placeNavigation.ts); isOutsideChina is the shared helper both use.

The two fixtures in the file that were cast to any now carry a type: the
key row and the fetch spy whose calls the reverse case reads back.

server/src/nest/maps/maps.service.ts

@@ -1,4 +1,5 @@
 import { Injectable } from '@nestjs/common';
+import { isOutsideChina } from '@trek/shared';
 import type {
   MapsSearchResult,
   MapsAutocompleteResult,
@@ -2819,7 +2820,9 @@ export class MapsService {
     lang?: string,
     opts?: { lane?: GeoLane; timeoutMs?: number; locality?: boolean },
   ): Promise<{ name: string | null; address: string | null }> {
-    // Amap answers first when it holds the keyed slot. Resolved at userId 0,
+    // Amap answers first when it holds the keyed slot, and only for a point it
+    // can possibly know: outside its box the call would cost a round trip to
+    // come back empty before Nominatim is asked anyway. Resolved at userId 0,
     // because most callers here have no person behind them (a booking import,
     // an Atlas tile, a right-click on a shared map): the chain stops at the
     // operator env var and the instance-wide row, and nobody's personal key is
@@ -2829,7 +2832,7 @@ export class MapsService {
     if (amap) {
       const latNum = Number.parseFloat(lat);
       const lngNum = Number.parseFloat(lng);
-      if (Number.isFinite(latNum) && Number.isFinite(lngNum)) {
+      if (Number.isFinite(latNum) && Number.isFinite(lngNum) && !isOutsideChina(latNum, lngNum)) {
         try {
           const answer = await amap.reverse(latNum, lngNum, lang);
           if (answer) return answer;