Navigation: a map_mismatch outcome when the console disagrees with a map #154

Part of #135.

When the console disagrees with a map, the walker fails today with a generic outcome (short_leg, "map didn't change", "unknown trainer") and nothing says the map is the suspect. Add a map_mismatch outcome to the shared walker and route log (#114) for: a leg blocked before the map's wall, a leg running past it, a warp step with no fade (or a fade the map doesn't have), dialogue no trainer or trigger explains, and a location banner for another map. It records the map, tile, expected vs observed and a screenshot, shows as one "MAP? …" line in the overlay and run record, and is not retried: the fix is to check that tile on the console once and correct the map JSON. A blocked leg can also mean the player is misplaced, so the line says "map or position".

Seen in BDSP 00.01 runs 8–15 (bedroom and Barry's stairs, door fades, Mom's and Barry's warnings, the Azure Flute ball).