[DbtProject] RFC: Update API post dogfooding

[maximearmstrong]

Summary & Motivation

This PR updates the API for 2 of the DbtProject attributes:

• target_path becomes output_path
  • Target path is the accurate name for the output path in dbt, but this was motivated by the following
    • We plan on adding more *Project classes, like SdfProject, and would like to standardize the naming across classes
    • DbtProject had both the attributes target and target_path, which means totally different things in this context which is slightly confusing for someone that is not familiar with all dbt concepts.
    • Edit: we will keep target_path as is to keep the name close to the dbt concept.
• manifest_preparer becomes preparer
  • This is mostly motivated by [DbtProject] Implement prepare_if_dev #22513, but also
    • we'd like to standardize the naming where possible, and preparer would make more sense with other classes like SdfProject
    • The DagsterDbtManifestPreparer doesn't prepare only the manifest, but also the dependencies with dbt deps
      • DagstetDbtManifestPreparer and DbtManifestPreparer would stay experimental are to be renamed in another PR.

Before being merged, these changes should be thoroughly discussed.

How I Tested These Changes

BK with already existing tests

[maximearmstrong]

• [DbtProject] Rename prepare_for_deployment by prepare_and_package in CLI #22653 : 2 dependent PRs (#22537 , #22546 )
• [DbtProject] RFC: Update API post dogfooding #22534 👈
• [DbtProject] Implement prepare_if_dev #22513
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @maximearmstrong and the rest of your teammates on Graphite

[github-actions]

Deploy preview for dagster-docs ready!

Preview available at https://dagster-docs-pwh04q0j4-elementl.vercel.app
https://maxime-ds-273-update-dbtproject-post-dogfooding-session.dagster.dagster-docs.io

Direct link to changed pages:

Approved by Rex