Add passthrough columns for USER + ORG and add support for updated passthrough format for TICKET

[fivetran-jamie]

PR Overview

This PR will address the following Issue/Feature:
fivetran/dbt_zendesk#122 --> will need to update transform README after this

This PR will result in the following new package version:

v0.11.2

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

Feature Updates

• Adds passthrough column support for USER and ORGANIZATION.
  • Using the new zendesk__user_passthrough_columns and zendesk__organizations_passthrough_columns variables, you can include custom columns from these source tables in their respective staging models. See README for more details on how to configure.
• Also updated the format of the pre-existing TICKET passthrough column variable, zendesk__ticket_passthrough_columns.
  • Previously, you could only provide a list of custom fields to be included in stg_zendesk__ticket. Now, you can provide an alias and transform_sql clause to be applied to each field (see README for more details).
  • Note: the package is and will continue to be backwards compatible with the old list-format.

PR Checklist

Basic Validation

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

• dbt run –full-refresh && dbt test
• dbt run (if incremental models are present) && dbt test

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

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

Detailed Validation

Please share any and all of your validation steps:

First, I ran with the new format across the board:

Everything passed

• dbt run

• dbt test

And I verified that the custom columns were present, filled with data, and properly aliased (if provided) in the WH

TICKET

USER

ORGANIZATION

I then reran, with

• zendesk__ticket_passthrough_columns using the old, currently employed format
• no values for the user and organization passthrough columns (just want to confirm these compile correctly)

Everything passed

• dbt run

• dbt test

In the WH, I confirmed that the staging ticket model had the custom columns, even if using the old variable format, which our macros are backwards compatible with

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

🛃

[fivetran-joemarkiewicz]

@fivetran-jamie these changes look good to me! Would you also be able to open a proactive FR on the transform package to allow us to expand the passthrough columns for User and Organization downstream as well.

Be sure to regen the docs, then this is good to go!