Move date typecasts into stg models

[katy-sadowski]

There are repeated typecasts of timestamp-->date in the OMOP models. To DRY up the code we can move these into the original stg models by creating a _date column in those models and carrying it through to the final models.

For example:

dbt-synthea/models/omop/drug_exposure.sql

Line 11 in 236f52a

, {{ dbt.safe_cast("drug_exposure_start_date", api.Column.translate_type("date")) }} AS drug_exposure_start_date

[katy-sadowski]

@lawrenceadams , I have addressed this Issue in commit ae79114

I accidentally pushed to main 🙈 I had branch protections relaxed for myself in the early days and forgot I was working on main. I have added these back now so I won't be able to do that in the future...oopsie! It runs and passes all tests on duckdb and Postgres. If you'd like to take a look / test the changes please do! What I did:

• Moved casts upstream where applicable to reduce repetition
• Changed all casts to use dbt.cast
• Spotted a couple other opportunities to use dbt macros (datediff, dateadd)
• Renamed some columns to indicate that they're datetimes, not dates (holdover from ETL-Synthea)

[lawrenceadams]

Oops! easily done (have done it myself before)!!

Excellent commit! 💪