Implement Alert_Status Table

[franTarkenton]

Currently, the alert_status is hard coded into the frontend components. When a new alert is created, or an alert is edited the frontend restricts what can go into these fields.

Ideally the options that can be entered into these fields should originate from the database, and then from there to the api.

This ticket would do the following:

• create a new migration that creates and populates the alert_status table.
• Modify the frontend so that the create and edit forms retrieve the status options for these fields from the api.
• Update the methods used to perform create / edit so that they build relationships vs. embedding the values into the alert table.
• Update the database docs

[franTarkenton]

duplicate to issue #42