make the list-agg columns conditionally tested

[dave-connors-3]

This is a:

• bug fix PR with no breaking changes
• new functionality

Link to Issue

DBX tests are failing in main because there is no support on Databricks for an order_by clause in the dbt.listagg macro, so we can't guarantee the order of the array of values in models where we report a list of violations within a single record.

Example:

 dbt show -s fct_source_fanout -t databricks --output json     
14:25:37  Running with dbt=1.8.8
14:25:38  Found 70 models, 72 data tests, 28 seeds, 8 sources, 1 exposure, 2 metrics, 779 macros, 1 semantic model
14:25:41  {
  "node": "fct_source_fanout",
  "show": [
    {
      "parent": "source_1.table_2",
      "model_children": "stg_model_2, int_model_4"
    },
    {
      "parent": "source_1.table_1",
      "model_children": "stg_model_2, stg_model_1"
    }
  ]
}
(dpe) 
dbt-project-evaluator/integration_tests on  dbx-test-fixes via (dpe) on ☁️  dev-admin (us-east-1) on ☁️   took 5s 
❯ dbt show -s test_fct_source_fanout -t databricks --output json
14:25:47  Running with dbt=1.8.8
14:25:48  Found 70 models, 72 data tests, 28 seeds, 8 sources, 1 exposure, 2 metrics, 779 macros, 1 semantic model
14:25:55  {
  "node": "test_fct_source_fanout",
  "show": [
    {
      "parent": "source_1.table_2",
      "model_children": "int_model_4, stg_model_2"
    },
    {
      "parent": "source_1.table_1",
      "model_children": "stg_model_1, stg_model_2"
    }
  ]
}

You can see the values are reversed, but identical.

This PR makes those columns conditional in our test configuration so that they are tested for all other adapters except DBX.

Since CI is off, i am running these tests locally!

Integration Test Screenshot

Checklist

• I have verified that these changes work locally on the following warehouses (Note: it's okay if you do not have access to all warehouses, this helps us understand what has been covered)
  • BigQuery
  • Postgres
  • Redshift
  • Snowflake
  • Databricks
  • DuckDB
  • Trino/Starburst
• I have updated the README.md (if applicable)
• I have added tests & descriptions to my models (and macros if applicable)

[dave-connors-3]

@b-per i did not test on trino bc i don't have it set up, and my BQ set up appears to be busted for some local issue -- i do not feel like this is a risky PR but lemme know if you want me to continue with manual tests

[b-per]

We should maybe technically check on target.type in ['spark', 'databricks'] as people running vanilla Spark would have the same issue as the people running databricks.

But if you don't feel like we need to do this change, happy to merge as-is as well.