Dynamic seed source configuration & workflow changes

[mkrahu-z2]

Describe your changes

Adjust the cms_synthetic_connector to leverage either the seed data (default behavior) or source data depending on the status of the demo_data_only variable in dbt_project.yml

How has this been tested?

Tested locally with duckdb, toggled the demo_data_only between true and false, when set to true, the connector loads the seeds from s3 as expected, when set to false the connector leverages the source locations as defined in models/_sources.yml

Reviewer focus

Review the implementation and see if this is intuitive for how we can create a 'default' behavior in connectors to allow them t run with synthetic demo data "out of the box" while easily switching to source locations once they have been implemented.

Checklist before requesting a review

• (Optional) I have recorded a Loom performing a self-review of my code
• My code follows style guidelines
• I have commented my code as necessary
• (New models only) I have implemented generic dbt tests to validate primary keys/uniqueness in my model
• I have added at least one Github label to this PR

(Optional) Gif of how this PR makes you feel

Loom link