hookup_manager stage one:  New tables for pending and active hookups (pair programming events).  Pivotal #75025008, 75025492

** Please accept the "Event-datetime-migration" first **
New tables for pending and active hookups (pair programming events).
Pivotal stories:
 "display list of pending events in a table", https://www.pivotaltracker.com/s/projects/982890/stories/75025008, and 
"display list of active/live hookups (i.e. hookups with live hangouts) in a separate table",https://www.pivotaltracker.com/s/projects/982890/stories/75025492. 
Added a hookups view, a hookups controller with an index service, and several methods to the events model to distinguish pending, active, and expired events.
@yaro, @yggie: I've been thinking about how to refactor the event model.  
Bryan created a user story months ago, 71075494, about refactoring the Event model, specifically referring to the use of IceCube.  Should we continue this discussion/activity as part of that user story?  
We have various options, including single table inheritance, creating a separate class for the occurrence/schedule related methods, creating a separate class for the event 'state' (expired, active, pending, etc).