Describe the bug - Required
When running dbt test, unexpected warnings:
20:17:16 Warning in test dbt_expectations_expect_column_values_to_be_in_type_list_input_layer__pharmacy_claim_coinsurance_amount__date__datetime__number__decimal__numeric__float__float4__float8__double__double_precision__real__float64__bignumeric (models\input_layer\input_layer__pharmacy_claim.yml)

20:17:16 Warning in test dbt_expectations_expect_column_values_to_be_in_type_list_input_layer__pharmacy_claim_copayment_amount__date__datetime__number__decimal__numeric__float__float4__float8__double__double_precision__real__float64__bignumeric (models\input_layer\input_layer__pharmacy_claim.yml)

20:17:16 Warning in test dbt_expectations_expect_column_values_to_be_in_type_list_input_layer__pharmacy_claim_deductible_amount__date__datetime__number__decimal__numeric__float__float4__float8__double__double_precision__real__float64__bignumeric (models\input_layer\input_layer__pharmacy_claim.yml)

In checking the generated tables, those columns were "INTEGER" where in earlier versions, they were "FLOAT".

Environment - Required

• Tuva project package version (e.g. 0.6.0): 0.14.18
• dbt version (e.g. 1.7):
• dbt type (e.g. dbt cloud or dbt CLI): cli
• Data warehouse (e.g. Snowflake): duck db

To Reproduce
Steps to reproduce the behavior:
Turn synthetic data on: in dbt_project.yml, use_synthetic_data: true (turn clinical_enabled: false for faster results)
Run dbt seed -s pharmacy_claim_seed --full-refresh
Run dbt run -s integration_tests, input_layer
Run dbt test -s input_tests
If an existing deployment, add --full-refresh to the calls.

Expected behavior
No issues with the fields coinsurance_amount, copayment_amount, deductible_amount.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.