Extend this API to support multiple disaster events simultaneously

[nihonjinrxs]

This entails several things:

• Close Figure out domain name situation when extending to multiple disaster events #74 by answering naming questions
• Creation of a new table and model to store disaster events and info
• Creation of association tables between shelters, distribution points, etc. and disaster events and associated model updates
• Views in the admin screens to add/update/archive disaster event records
• Update of API endpoints to require disaster event filtering
• Removal of references to specific storms in naming within the app (i.e. repo name, db info, etc.)
• Redeploy of new clean instance with generic naming
• Repopulation of data from old instance, and population of association tables as needed for existing data
• Repointing of front end apps to new instance with appropriate filtering
• Decommission of old production instance

[omnilord]

👍 Drilling down a little further, I was think the event model should include geometry features for the effected area mapping, such as an epicenter with radiants, or a line with time-based polygons representing the affected regions. This would also provide information for the map to use for centering and zooming maybe even add some of that summary data about a specific region. I've been thinking about this for a while now.

[nihonjinrxs]

@omnilord, you've been driving this one for a while now. Can you update where we are on this one, and possibly push what you've got on this up to a branch/PR?