Raise deprecation warning if installed package overrides built-in materialization

[MichelleArk]

Housekeeping

• I am a maintainer of dbt-core

Short description

We are deprecating the ability for installed packages to override built-in materializations without explicit opt-in from the user.

Users should still be able to wrap the built-in materialization in their root project to avoid this deprecation warning. e.g:

{% materialization view, default %}
 {{ return(my_cool_package.materialization_view_default()) }}
{% endmaterialization %}

Acceptance criteria

• Overriding a built-in materialization from an installed package raises a deprecation warning
• Using a custom materialization from an installed package does not raise a deprecation warning
• Using a built-in materialization package override from the root project via a wrapping materialization is not deprecated, no warning

Suggested Tests

reads from acceptance criterea

Impact to Other Teams

N/A

Will backports be required?

yes -- to 1.7 and 1.6, 1.5 will be EOL'd in a few days.

Context

#9164

[FishtownBuildBot]

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