The ordering goes like this:
- Get the original meeting object from the DB
- Convert it to UTC (becomes: meeting_utc)
- Get the next meeting depending on its recursivity, using meeting_utc
- Convert to the user's timezone.
The bug was that we were converting next_meeting to the user's timezone
based on the timezone of the original meeting, but next_meeting is based
on meeting_utc, so it is already in UTC and therefore we need to convert
its timezone from UTC.