Add Map Point photos

[KacperKozak]

Map Point photos become durable Hosted Assets. The phone normalizes and uploads them natively, owners attach them to server-owned Map Points, and signed-out readers receive bounded public images. Transfer state remains reliable across offline periods, process death, sign-out, and Account changes.

Warning

Risk: High. This adds native media processing, authenticated uploads, durable retry and delete jobs, and server attachment state.
Complexity: High. It coordinates iOS and Android normalization, Asset identity, Map Point attachment, and background lifecycle.
DB: Schema and data. It adds durable Asset jobs and normalized local files. The parked Map Point media prototype needs no migration because it never shipped enabled.

Tasks

• [Assets] 1 - Normalize and upload Map Point photos #312
• [Assets] 2 - Attach Map Point photos #313
• Server: vescape-app/vescape-server#29 and vescape-app/vescape-server#33

Blocked by

• vescape-app/vescape-server#33

Description

Photos picked or captured on-device pass through one native pipeline. It applies orientation, strips metadata including GPS, limits dimensions without upscaling, and produces WebP with JPEG fallback. A client-generated UUID identifies each Asset before the first upload, so an ambiguous retry addresses the same Asset instead of creating an unknown orphan.

Native owns normalized files, remote identity, retry policy, and deletion through a durable job queue. JS renders state and sends intents. Map Point owners can add, remove, replace, and retry photos while public readers receive bounded server-resized images.

Map Points remain server-owned. Upload and attachment use their own Asset and Map Point endpoints. If upload succeeds but attachment fails, native retries with the Asset ID it already holds and does not upload the bytes again.