fix: improve tourism info data consumption

[ClarusIubar]

Summary

• render KTO tourism image, summary, description, category, district, source, and homepage link in the information sheet
• pass an AbortSignal through the tourism API client and stop indefinite tourism loading after a configured timeout
• add component/API regression tests and completion evidence for TSK-013-01

Architecture Boundary Gate

• Responsibility map: tourismClient owns the Worker consumer request; useAppCoordinatorEffects owns request lifecycle/timeout; TourismInfoSheet owns normalized TourismPlaceItem presentation.
• Dependency direction: UI effect -> API client -> fetchJson; presentation component -> TourismPlaceItem. Browser code still does not call KTO/OpenAPI, Supabase, or admin import APIs directly.
• Test seam: component render assertions for rich KTO fields; API client assertion for RequestInit.signal forwarding.
• Scope map: frontend data consumption and timeout guard only. API path, response shape, DB schema, OAuth flow, and curated place stamp/review flow unchanged.
• Architecture risk: KTO info pins must stay information-only, not curated place action surfaces; this PR does not add stamp/review/feed actions.

Validation

• npm.cmd run check:numeric-literals
• npm.cmd run lint
• npm.cmd run typecheck
• npm.cmd run test:unit -- tourism-info-sheet tourism-client
• npm.cmd run test:unit
• npm.cmd run test:integration
• npm.cmd run test:regression
• npm.cmd run test:e2e
• npm.cmd run build
• git diff --check
• UTF-8 strict read for changed source/test files

Closes #421