fix: use target.type instead of target.name for Databricks float precision exclusion

The equality test for fct_test_coverage was failing on Databricks when using
custom target names (e.g., 'dx') because the exclusion logic checked target.name
instead of target.type. Also added test_to_model_ratio to the exclusion list
as it has the same float32 precision issue.

Author: b-per

integration_tests/seeds/tests/tests_seeds.yml

@@ -32,8 +32,8 @@ seeds:
               - total_models
               - total_tests
               - tested_models
-              - "{{ 'test_coverage_pct' if not target.name in ['duckdb', 'databricks', 'trino'] else 'tested_models' }}"
-              - test_to_model_ratio
+              - "{{ 'test_coverage_pct' if target.type not in ['duckdb', 'databricks', 'trino'] else 'tested_models' }}"
+              - "{{ 'test_to_model_ratio' if target.type not in ['duckdb', 'databricks', 'trino'] else 'tested_models' }}"
               - staging_test_coverage_pct
               - intermediate_test_coverage_pct
               - marts_test_coverage_pct