Test Durham API import

[copelco]

Primarily the forms. We want to make sure we only update the intended fields, e.g. not replace property_id.

[copelco]

Or, for example, what if we fix the lat/lng coordinates in the admin. On the next import, we should probably skip importing the location.

[tamcap]

Would it make more sense to just have a list of fields we want to overwrite? I.e. we assume our db takes precedence over the Durham one, unless it's a change of address.

[copelco]

I think it depends on how the form is implemented, but yes. Establishments use the exclude meta property. In the end, I want a regression test to fail if we add a new field and it gets overwritten (as in, we forget to add it to exclude).