incorporate timezone and daylight tables

[fivetran-jamie]

Are you a current Fivetran customer?

fivetran made PR

What change(s) does this PR introduce?

• adds daylight_time and time_zone staging models and macros
• adds seed data for new source tables
• adds postgres run to circle ci setup (the transform package already had it but not the source 🤷‍♂️ ) --> ok removed this for now as i can now see that we probably didn't include postgres here because it's a bit complicated... i can address this later but just wanna make sure it runs on the other warehouses for now
• adjusts circle ci dbt runs to be a bit more thorough...
• adds documentation + tests for the new tables/models
• update package version ?

Does this PR introduce a breaking change?

• Yes (please provide breaking change details below.)
• No (please provide explanation how the change is non breaking below.)

uhhhhhh yes i think??? anyways v0.8.0 of the transform package will be a breaking change right?

Is this PR in response to a previously created Issue

• Yes, Issue BUG - UTC Timezones for schedules need to be reworked dbt_zendesk#62
• No

How did you test the PR changes?

• CircleCi
• Other (please provide additional testing details below)
  tested locally on BQ

Select which warehouse(s) were used to test the PR

• BigQuery
• Redshift
• Snowflake
• Postgres
• Databricks
• Other (provide details below)

Provide an emoji that best describes your current mood

🐶

Feedback

We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your feedback on our existing dbt packages or what you'd like to see next.

[fivetran-joemarkiewicz]

The addition of the time_zone and daylight_time tables looks great @fivetran-jamie! The hoops you have to jump through to extract the offset is pretty wild. Great job!

I have a few small inline comments. Additionally, a few things that we should update before we merge.

• Add the description of the updates here to the CHANGELOG
• Since we are swapping out the start/end_time_utc fields in the schedule model we will want to have this be a breaking change on the source as well. Can you be sure to reflect that in this PR.
• Regenerate the docs
• The Postgres CircleCi may just need the default column to be quoted since it is a reserved word 🤷