Late night events:  Previously could not be created due to validation from_before_to. PT: 75084268 

Can now create events that start just before midnight UTC and end after midnight.  PT: 
Here are the declarations for the relevant fields in schema
    t.date     "event_date",                                null: false
    t.time     "start_time",                                null: false
    t.time     "end_time",                                  null: false
The start_time and end_time are just times, not dates, so if we're to allow events that bridge UTC midnight, then we can't simply validate that the end_time is greater than start_time... the dates matter.  But, we only have one date, which is implicitly the start_date.  My approach is to assume that events can't be more than 24 hours, and if the user specifies an end_time earlier than the start_time, then they intend the end_date to be the next day.  This is a real problem because if someone in California specifies an evening event, e.g. 4:30 pacific time, which is 11:30 UTC, then their event will be rejected.  I think that this solution is good... the best one short of getting rid of the event_date and changing start_time and end_time both to datetime's instead of simply times.