[Feature] Support passing a flag to suppress errors arising from removing a versioned, contracted model

[ramiz-bozai-dbt]

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

With changes made in dbt v1.9, removing a contracted model that is also versioned raises an error. This causes issues in a use case where I would like to put out a "pre-release" and make changes prior to making this available for public consumption.

In an ideal situation, there could be two paths forward:

1. dbt raises a warning instead of an error when it sees a breaking change to a versioned, contracted model and the version is greater than the model's existing latest_version
2. (even better) if we're interested in enforcing this, there could be an option for users to pass a flag such as bypass_prerelease_warnings to allow for users to work around this.

Describe alternatives you've considered

The simplest alternative is to either remove the model versioning which allows this to become a warning. Alternatively, you can remove the model altogether then create a new release to add it back. Neither option is particularly conducive to shipping fast.

Who will this benefit?

Teams looking to "pre-release" models which are not ready for public consumption just yet.

Are you interested in contributing this feature?

N/A

Anything else?

No response