Update/crm api v3 - contact merge audit removed

[fivetran-jamie]

Are you a current Fivetran customer?

internal

What change(s) does this PR introduce?

aligns with recent changes to the hubspot API

• adds the new property_hs_calculated_merged_vids field to the contact model/macro and its seed data
• explicitly casts all timestamp fields as timestamps
• adds BigQuery-specific logic since the above connector change is blocked on BQ. Thus, they will have to use the old behavior, but we want to make it so that they can switch to the new way if they want (by setting hubspot_contact_merge_audit_enabled to FALSE.

Did you update the CHANGELOG?

• [x] Yes

Does this PR introduce a breaking change?

• [x] Yes (please provide breaking change details below.)
• [ ] No (please provide an explanation as to how the change is non-breaking below.)

default behavior is different for most users (though they should end up with the same result...so maybe not?)

Did you update the dbt_project.yml files with the version upgrade (please leverage standard semantic versioning)? (In both your main project and integration_tests)

• [x] Yes

Is this PR in response to a previously created Bug or Feature Request

• [x] Yes, Issue/Feature https://github.com/fivetran/dbt_hubspot_source/issues/97 + https://github.com/fivetran/dbt_hubspot/issues/97
• [ ] No

How did you test the PR changes?

• [x] Buildkite
• [x] Local (please provide additional testing details below)

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

• [x] BigQuery
• [x] Redshift
• [x] Snowflake
• [x] Postgres
• [x] 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](https://www.surveymonkey.com/r/DQ7K7WW) on our existing dbt packages or what you'd like to see next.

[fivetran-jamie]

will regen docs before merging