Dagster DBT w/ DBT >=1.9 Breaks With Unit Tests Due to Enabled Attribute

[cwe5590]

What's the issue?

In DBT 1.9 dagster-dbt seems to break if a project contains unit tests. This seems to happen because of the addition of enabled attribute to the unit test config: https://github.com/dbt-labs/dbt-core/pull/10831/files#diff-b4756f21e0fa65b77bb36828994d3a758360b5acd05bbb9526b5bfe399194617L176.

This unit_test.config looks like it needs to be of type <class 'dagster_dbt.utils.select_unique_ids_from_manifest.._DictShim'> instead of a dict to allow for dot access.

.venv/lib/python3.12/site-packages/dbt/graph/selector.py:178: in _is_graph_member
    return unit_test.config.enabled
E   AttributeError: 'dict' object has no attribute 'enabled'

DBT representation:

unit_test.business_intelligence.[OBFUSCTATED].test_is_[OBFUSCTATED]:UnitTestConfig(_extra={}, tags=[], meta={}, enabled=True)

Representation of unit test from a manifest loaded from file via dbt_assets:

unit_test.business_intelligence.[OBFUSCTATED].test_is_[OBFUSCTATED]:  {'tags': [], 'meta': {}, 'enabled': True}

What did you expect to happen?

No errors to occur

How to reproduce?

Add unit tests to a dbt project and load via manifest file using the dbt_assets decorator

Dagster version

1.9.8

Deployment type

None

Deployment details

No response

Additional information

No response

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.

[garethbrickman]

Duplicates #27007