Bug/postgres performance

PR Overview

This PR will address the following Issue/Feature:

Internal ticket
124

This PR will result in the following new package version:

v1.7.3 non-breaking since there are no schema changes and results are the same as prior

Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:

Performance Improvements

Updated the sequence of JSON parsing for model fivetran_platform__audit_table to reduce runtime.

Bug Fixes

Updated model fivetran_platform__audit_user_activity to correct the JSON parsing used to determine column email.

Under the hood

Updated logic for macro fivetran_log_lookback to align with logic used in similar macros in other packages.

PR Checklist

Basic Validation

Please acknowledge that you have successfully performed the following commands locally:

[x] dbt run –full-refresh && dbt test
[x] dbt run (if incremental models are present) && dbt test

Before marking this PR as "ready for review" the following have been applied:

[x] The appropriate issue has been linked, tagged, and properly assigned
[x] All necessary documentation and version upgrades have been applied
[x] docs were regenerated (unless this PR does not include any code or yml updates)
[x] BuildKite integration tests are passing
[x] Detailed validation steps have been provided below

Detailed Validation

Please share any and all of your validation steps:

See internal ticket for data quality validation
Runtime comparison:
- Note: this was tested on a subset of the log data limited to about 250k rows. This was done by filtering the staging log model using filter

where cast(created_at as date) < cast('2024-05-10' as date)
and cast(created_at as date) >= cast('2024-05-07' as date)

which produces these results:

v1.7.2 run: ~ 1hr

v1.7.3 run: ~ 10 mins

If you had to summarize this PR in an emoji, which would it be?

🌳

fivetran / dbt_fivetran_log