Action "types" and other fields.

[ryanmdoyle]

With #36 We can now post a new "action" from the front-end.

We still have some issues that need to be discussed along with Actions.
[ ] Who controls visibility?
[ ] What types of "actions" should we have?

Currently, we are posting new actions to the "/events" route. I have hard-coded in the "action_type_id" as 1, assuming that the only actions we currently have are these "events." Presumably, later on, we would have other actions, like "announcements" and those would have another action_type_id.

We also have visibility and the user_id hard-coded as "true" and 1, respectively. I wan;t able to figure out in less than a few minutes what fields were required on the db end, so I just make the front-end query contain all the fields that the backend seemed to have.

I assume this is a longer-term issue, but eventually, we will need to have a list of different actions. I see that is in the data visual of the db but not sure what is there at the moment.