Add national member data

@DSASanFrancisco/portal-members

I wrote a script to upload the membership data from csv into our membership portal.

This adds additional membership information including physical address, phone numbers, etc. While I think we should be concerned with security regarding this information. I don't think this is any worse than the current security of sharing this information via Google Sheets with all of leadership. I think it would be better to have more limited access though a membership portal where we can't accidentally turn on link sharing and expose the data to anyone with the link.

The new schema adds an Identity which is essentially additional identifiers for a user, alongside the identity provider's name. I didn't see a need to normalize it more than a basic enum for the id_provider field.

I ran this script multiple times on production data until I was reasonable sure that it was idempotent. If we were to include this script, it should be safe to run on new membership lists that we get without blowing away our old data.

It would be nice to write some sort of system of hooks to support adding / inviting people to Auth0, Google Hangouts, Slack, etc upon upload, but I'm leaving that for a follow up PR. I did try to put in place some foundation for future scripts using the runjob.py script and the jobs module.