People: add distinct mailing classification options to offices

[jessemortenson]

Adds new classification options for an office: district-mail and capitol-mail.

Plural pulled in a new data source for People, that helps us add some data points that were not possible to scrape, and also still allows us to publish public data about elected officials.

This new dataset includes office addresses in some jurisdictions that are distinct between the physical location of the office and the mailing address. Adding these new classifications would allow us to have both data points in the People repo (otherwise those classifications are deemed invalid).

Possible downside: could move some data that was previously classified as district or capitol to one of the new classifications. Client code may not know how to handle these new classifications.

Alternative: leave the "mailing" addresses out of the People repo.

[NewAgeAirbender]

I think it's smart to add the data as distinct types

[chris-erickson]

For our purposes we check if the type is capitol or district and set that as a mailing address for each type. Sometimes we need to do some inference if that type isn't present based on if the city matches the Capitol city. I think to accommodate this new change we'd just check for this new attribute and use those addresses first, and fallback to the existing logic if not present. At a glance this doesn't look excessively complicated but any kind of advance notice of it happening or even just examples of the resulting data change as it relates to the API would be great.

I could see a case where we might store both so we can tell people where a physical office is more accurately, but that's not a very common use case for us.

[jessemortenson]

Thanks for the feedback @chris-erickson - that's helpful. I'll merge this in, and then open up a couple PRs that show the data changes in a couple jurisdictions, will tag you in those.