2 fixes for Databricks compatibility

Describe your changes

Please include a summary of any changes.

I added ltrim.sql macro which uses adapter.dispatch to pipe in different logic for different databases. Main reason is that Databricks' LTRIM function arguments are reversed!! https://learn.microsoft.com/en-us/azure/databricks/sql/language-manual/functions/ltrim

I also updated normalized_input__int_bill_type_voting.sql to use this macro. Confirmed that this is the only model that uses ltrim today.

Lastly, I added some format options to databricks__load_seed which allow quotes to be escaped properly and allow for line breaks. This fixes load errors for clinical_concept_library__clinical_concepts and terminology__snomed_ct (also observed by Sean Cofoid)

How has this been tested?

Please describe the tests you ran to verify your changes. Provide instructions or code to reproduce output.

I performed a dbt compile on the above-mentioned model to make sure it was producing correctly formatted query.

For the seeds, I loaded seeds using the original logic and the new logic. And I confirmed that the only differences were in the above-two seeds. All other seeds had identical sizes.

Reviewer focus

Please summarize the specific items you’d like the reviewer(s) to look into.

Confirm if there are any adapters that have a similar issue

Checklist before requesting a review

[x] I have added at least one Github label to this PR (bug, enhancement, breaking change,...)
[x] My code follows style guidelines
[ ] (New models) YAML files are categorized by sub folder and models listed in alphabetical order
[ ] (New models) I have added a config to each new model to enable it for claims and/or clinical data
[ ] (New models) I have added the variable tuva_last_run to the final output
[ ] (Optional) I have recorded a Loom to explain this PR

Package release checklist

[ ] I have updated dbt docs
[ ] I have updated the version number in the dbt_project.yml

tuva-health / tuva