[Regression] Intra-project ambiguous/duplicate refs checking has been disabled

[milevin]

Is this a regression in a recent version of dbt-core?

• I believe this is a regression in dbt-core functionality
• I have searched the existing issues, and I could not find an existing issue for this regression

Current Behavior

Parsing on the attached project succeeds:

> dbt parse
16:34:15  Running dbt...
16:34:16  Unable to do partial parsing because saved manifest not found. Starting full parse.
16:34:16  Performance info: /Users/mlevin/dbt/double_ref/target/perf_info.json

The project has a seed and model using the same file name. A ref in a downstream model references this file name. The resolver silently picks the seed over the model.

Expected/Previous Behavior

It should fail fast throwing an ambiguous ref error at parse time.

The regression, I believe, was introduced by this change:

#7374

Steps To Reproduce

double_ref.zip

Relevant log output

Environment

- OS:
- Python:
- dbt (working version):
- dbt (regression version):

Which database adapter are you using with dbt?

No response

Additional Context

Internal slack thread

[graciegoheen]

If this has been the behavior since 2023, then I believe we need to treat this as a behavior change (put the fix behind a behavior change flag).

[MichelleArk]

closed via restore DuplicateResourceNameError exception within a package #12183

[FishtownBuildBot]

Opened a new issue in dbt-labs/docs.getdbt.com: dbt-labs/docs.getdbt.com#8221