Align / Unify parsing of map infos

parse_mapinfo_for ... contain a large amount of duplicated code

map info now may work differently than other sources - is this intentional/convenient?

Locate the parse_mapinfo_for implementation and compare its parsing path with the other metadata sources. Identify which duplicated logic should be shared and whether the differing map-info behavior is intentional. Done means map info follows the same parsing conventions without unintended behavior changes; no specific test is named in the issue.

Written by the indexing model from the issue text.