Update expected data keys based on recent warehouse normalization changes

[rudokemper]

• [ ] Remove p__ prefix for property keys.
• [ ] Adapt geometry separator (right number of underscores)
• [ ] Ignore new metadata fields introduced by frizzle
• [ ] Handle media attachments from datalake (Kobo and ODK file storage conventions)
• [ ] Modify database columns for existing Mapeo imports to match the new expected fields

[IamJeffG]

You may know this but the changes related to p__ prefix and geometry separator are all captured in the new {table}__columns table. So if guardianconnector-map is going to look into that table already, then it won't need to also encode its own special rules about p__ and geometry.

[IamJeffG]

In https://github.com/ConservationMetrics/frizzle/issues/99 I was able to migrate kawana and bcm deployments without changing most of the table column names. There were a couple changes even in these but I'd imagine they are immaterial to you: (i) drop "type" column, (ii) rename p___id to _id. But the other columns should be unchanged from before.

On the other hand, this means that different deployments now use different heuristics (from each other) to generate column names. So ultimately, for property naming, guardianconnector-map needs to look up the *__columns table.

Note that the geometry columns have remained unchanged from before and also will remain constant between different deployments: this might help you keep things simple here in this repo.

[rudokemper]

Sounds good. I will rework this repo to use the column names table after we finish the other migration tasks, and once we figure out authenticated access to media attachment files. (I'll handle both in the same batch of work.)