Send emails to users with localized timezone

[ipwnponies]

This adds support for sending emails to user's with localized timezone. Currently user timezone information does not exist so this change should not result in visible changes.

This still needs an end-to-end test but I'm unsure how to do this:

• Send test email to ensure timezone works
• Do dataprovider sync to test the model change.

[kentwills]

@ipwnponies I am a little concerned about this line. This doesn't seem backward compatible. I would expect this to blow up for older models that don't have a timezone property.

[ajm188]

We should version beans - that way you can't run this code without also picking up the changes to the User model

[kentwills]

Agreed, we should version. Though I am not sure that addresses the problem here. I think that if we have old records that don't have the timezone entry (our current prod instance) and we update the model and attempt to access user.timezone, it will say that timezone does not exist on the user even though the model is defined properly.

[ajm188]

Wouldn't user.timezone just return None then?

[kentwills]

If that is the case then we should be gtg. Just want to verify that behavior.

[ajm188]

Just want to verify that behavior

I leave that in the very capable hands of @ipwnponies :)

[ny2ko]

I set something similar up for my fork for Twitch with an extra addition: I retrieve the user's timezone on the frontend and pass it to the backend for storage. Additionally, becoming timezone aware helps fix the breaking test_get_meeting_participants which starts to fail when clocks move back

[ymilki]

beans has changed a lot since 2017. We do need to fix the timezone issues, but at this point, a new PR would be more appropriate. #145 #141 #122 are tracking some specific symptoms related to timezone.