Prefer internal macros when called explicitly

[jtcohen6]

resolves #5720

Description

• If an internal macro is called as {{ dbt.internal_macro() }}, prefer the version actually defined in the internal (dbt) namespace. All of these macros should be dispatched, and still overrideable by end users, using more explicit nomenclature + config patterns.
• If an internal macro is called as {{ internal_macro() }} (no namespace), it will follow global macro resolution order, and a root project reimplementation of internal_macro will take precedence

I haven't been able to come up with a concrete example of a behavior (however gnarly or undocumented) that worked before this change, and would be broken after. Let's run some functional tests and find out what breaks!

If things seem to be working, I can pull the reproduction case from #5720 (comment) into a new functional test.

Checklist

• I have read the contributing guide and understand what's expected of me
• I have signed the CLA
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
• I have run changie new to create a changelog entry

[github-actions]

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide.

[emmyoop]

The actual change looks fine. However, this isn't the correct test file format. I have the appetite to fix up the file formatting and will push the changes up to your branch.

[jtcohen6]

However, this isn't the correct test file format.

guilty!

I have the appetite to fix up the file formatting and will push the changes up to your branch.

thank you so so so much @emmyoop 🙏

[emmyoop]

Close and reopen to re-kick off snyk and make sure my changes didn't cause anything bad!