Feature/add union data

[fivetran-jamie]

PR Overview

This PR will address the following Issue/Feature: https://github.com/fivetran/dbt_hubspot/issues/130

This PR will result in the following new package version:

v0.16.0

Please detail what change(s) this PR introduces and any additional information that should be known during the review of this PR:

• includes source_relation in every:
  • join
  • window function partition
  • generated surrogate key
  • model uniqueness test
• documents unioning ability in README
• adds yml docs for source_relation
• adds some missing documentation that was in the source README but not the transform
• kinda by accident included changes from https://github.com/fivetran/dbt_hubspot/pull/132, which might be merged to main prior to this PR

dbt_hubspot v0.16.0

🎉 Feature Update 🎉

• This release supports running the package on multiple Hubspot sources at once! See the README for details on how to leverage this feature (PR #133).

📝 Documentation 📝

• Included documentation around dbt-core versions and disabling source freshness tests. Previously, we included this in the source package README but had missed the transform README (PR #133).
• Tweaked the description of hubspot__deal_changes to better reflect the grain of the model (PR #132).

🛠️ Under the Hood 🛠️

• Updated the maintainer PR template to resemble the most up to date format.

PR Checklist

Basic Validation

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

• [x] dbt compile
• [x] dbt run –full-refresh
• [x] dbt run
• [x] dbt test
• [x] dbt run –vars (if applicable) different permutations of passthrough columns -- ran with diff hubspot__pass_through_all_columns values and specific passthrough columns with add_property_label: true

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

• [x] The appropriate issue has been linked and tagged
• [x] You are assigned to the corresponding issue and this PR
• [x] BuildKite integration tests are passing

Detailed Validation

Please acknowledge that the following validation checks have been performed prior to marking this PR as "ready for review":

• [x] You have validated these changes and assure this PR will address the respective Issue/Feature.
• [x] You are reasonably confident these changes will not impact any other components of this package or any dependent packages.
• [x] You have provided details below around the validation steps performed to gain confidence in these changes.

See Hex notebook linked in Height

Standard Updates

Please acknowledge that your PR contains the following standard updates:

• Package versioning has been appropriately indexed in the following locations:
  • [x] indexed within dbt_project.yml
  • [x] indexed within integration_tests/dbt_project.yml
• [x] CHANGELOG has individual entries for each respective change in this PR
• [X] README updates have been applied (if applicable)
• [ ] DECISIONLOG updates have been updated (if applicable)
• [X] Appropriate yml documentation has been added (if applicable)

dbt Docs

Please acknowledge that after the above were all completed the below were applied to your branch:

• [ ] docs were regenerated (unless this PR does not include any code or yml updates) - post approval

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

🍨