Add config enabled for disable-able sources

[epapineau]

Pull Request
Are you a current Fivetran customer?

Elize Papineau, Senior Analytics Engineer, dbt Labs
Yes, working on behalf of a customer using Fivetran
What change(s) does this PR introduce?

Passes the configurable variables to config: enabled to prevent running source freshness on disabled models
Did you update the CHANGELOG?

• Yes

Does this PR introduce a breaking change?

• Yes (please provide breaking change details below.)
• No (please provide an explanation as to how the change is non-breaking below.)
  It extends use of existing variables
  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)

• Yes

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

• Yes, Issue
• No

How did you test the PR changes?

• CircleCi
• Local (please provide additional testing details below)

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]

@epapineau thanks so much for making these changes! They look great on my end, but I actually just discovered that there is a native way we can disable these sources without needing to use the meta config and override the freshness macro!

The best option would be to disable the source entirely instead of the meta config. Thankfully, the only change needed in your PR is to swap meta for config. Would you be able to make those changes and see if they work as intended on your end?

[fivetran-joemarkiewicz]

@epapineau thanks so much for making the changes 😄 I made two small changes to bump the version in our integration tests project and also made a small edit to the CHANGELOG.

With that, this PR is good to go! Thanks so much for your collaboration and contribution to the package 🙌 These packages are made better by contributors like yourself adding to the code base. I will merge this and plan to cut a release later this morning.