refactor(place-import): the Naver pager declares its page result, so the moved reader passes the strict ratchet

The reader left places.service with four strictNullChecks errors that a new
file may not carry. Declaring fetchPage's result as a page or a list import
error lets the 'error' check narrow it; the places and maps entries drop off
the strict baseline.

server/scripts/strict-baseline.json

@@ -76,7 +76,6 @@
   "src/nest/journey/journey.dto.ts": 2,
   "src/nest/journey/journey.mcp.ts": 1,
   "src/nest/llm-parse/mime-email.ts": 1,
-  "src/nest/maps/maps.service.ts": 1,
   "src/nest/maps/providers/amap.provider.ts": 1,
   "src/nest/mcp-transport/mcp-transport.service.ts": 4,
   "src/nest/memories/immich.controller.ts": 1,
@@ -92,7 +91,6 @@
   "src/nest/packing/packing.mcp.ts": 1,
   "src/nest/places/places.controller.ts": 2,
   "src/nest/places/places.mcp.ts": 5,
-  "src/nest/places/places.service.ts": 4,
   "src/nest/platform/discovery-metadata.service.ts": 3,
   "src/nest/plugins/host/plugin-jobs.ts": 1,
   "src/nest/plugins/host/rpc/host-surface.rpc.ts": 8,