Michelle Ark

From refinement: * At what level should the retry logic live? Options: GH workflow (all we can really do if we fail at the tox step), using existing retry/fallback code...

Not sure why the `Check Artifact Changes` check is failing even though there are no dbt/artifacts changes: https://github.com/dbt-labs/dbt-core/actions/runs/7980936313/job/21791611600?pr=9605 It's still pretty new, will look into that separately! Using the `artifact_minor_upgrade`...

Lowering priority of this given manual fixes to several unit tests affected by this issue: https://github.com/dbt-labs/dbt-core/pull/9897

## Spike Report / Update ### Current State dbt-snowflake, dbt-bigquery, and dbt-spark support mocking inputs with complex types in unit testing, including json and array types. tests here: * dbt-snowflake:...

A simple approach that _might_ work here to achieve an 'maximally parallelized execution mode' would be to modify the [get_graph_queue](https://github.com/dbt-labs/dbt-core/blob/9836f7bdef00b7cb912ad88ab1bbbfbd4dc4b312/core/dbt/graph/selector.py#L308-L316) method to accept an optional config that builds the graph...

Added this issue to the 'Stabilize External Interfaces' Epic under `Artifacts` since it plays nicely with our efforts to make the base artifact dataclasses 'plain old data objects'

Updated this issue to be scoped to the _usage_ of Replaceable in dbt-core, since it is now defined in dbt-common. Its full deletion can be done as a separate issue...

An initial pass was taken here: https://github.com/dbt-labs/dbt-core/pull/7844 but will likely need to start from scratch given the artifact + dbt-common refactors since it was initially spiked.

It looks like `WITH RECURSIVE` is supported for most of the dbt Labs supported adapters: * :white_check_mark: BigQuery: * https://cloud.google.com/bigquery/docs/recursive-ctes :white_check_mark: Snowflake: https://docs.snowflake.com/en/sql-reference/constructs/with#syntax * :x: Spark: * can't find any...

For implementation: * It looks like the extraneous select * is coming from the `unit` materialization, [where we create a temp empty table of the model being tested](https://github.com/dbt-labs/dbt-adapters/blob/main/dbt/include/global_project/macros/materializations/tests/unit.sql#L11) using `get_create_table_as_sql(True,...