[Feature] Automatically attempt a full parse before returning a parse error

[siljamardla]

Is this your first time submitting a feature request?

• I have read the expectations for open source contributors
• I have searched the existing issues, and I could not find an existing issue for this feature
• I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature

Feature

Before returning a parse error, always attempt a full parse.

Sample use case

• Make (significant) changes to source files
• Work as usual, doing a dbt parse or compile (dbt will do a partial parse)
• Often enough you'll get an error similar to this:

Compilation Error
  Model 'XXX' (models/XXX.sql) depends on a source named 'YYY.ZZZ' which was not found

• Delete the target folder or delete the manifest file or do dbt clean && dbt deps to trigger a full parse
• Parse/Compile again and the error goes away

Experienced dbt users will know what do most of the time, but even they get caught off guard every now and then. Inexperienced dbt users will almost always require support, halting their work process.
At Bolt, this happens almost every week, multiple dbt users get stuck until someone instructs them to trigger a full parse.

Describe alternatives you've considered

No response

Who will this benefit?

No response

Are you interested in contributing this feature?

No response

Anything else?

No response