Better support of times & timezones

- use `LocalDateTime` instead of `DateTime' for client facing timestamps.  these values are just a timestamp without any timezone (conference fields: registration start & end times, event start & end times, early registration cutoff
- upgrade to latest sql2o version which adds support for `LocalDateTime`
- use separate Json serializers for `DateTime` and `LocalDateTime`
I gave that some more thought, and I agree with you that it's wise to use `DateTimeZone`.  In addition to type enforcement like you mentioned, it cuts down on doing "casts" within the code too.