Per the docs of 1.7.13:

[dagster-dbt] During development,DbtProject no longer prepares the dbt manifest file and dbt dependencies in its constructor during initialization. This process has been moved to prepare_if_dev(), that can be called on the DbtProject instance after initialization. Check out the API docs for more: https://docs.dagster.io/_apidocs/libraries/dagster-dbt#dagster_dbt.DbtProject.prepare_if_dev.

@izzye84 already did the other piece in #100, of switching the dagster-dbt CLI arguments.

This won't have an impact on branch deployments or our data-eng-prod deployment, but will be useful for local dev