add config support for macros

[ash2shukla]

Resolves #12383
Resolves #9447

Problem

At present we can only declare meta and docs properties on top level whereas they should be supported inside the config as well.

Solution

Create config property with meta and docs and populate them in patch parser with precedence to config.meta and config.docs.

Checklist

• I have read the contributing guide and understand what's expected of me.
• I have run this code in development, and it appears to resolve the stated issue.
• This PR includes tests, or tests are not required or relevant for this PR.
• This PR has no interface changes (e.g., macros, CLI, logs, JSON artifacts, config files, adapter interface, etc.) or this PR has already received feedback and approval from Product or DX.
• This PR includes type annotations for new and modified functions.

[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.

[github-actions]

Additional Artifact Review Required

Changes to artifact directory files requires at least 2 approvals from core team members.

[ash2shukla]

This could be handled by defining UnparsedMacroUpdate.config with docs: Docs as well but that breaks the pattern of only needing to inherit from HasColumns.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.47%. Comparing base (9bb6ebe) to head (70064d2).
⚠️ Report is 14 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #12559      +/-   ##
==========================================
- Coverage   91.39%   90.47%   -0.92%     
==========================================
  Files         203      203              
  Lines       25494    25586      +92     
==========================================
- Hits        23301    23150     -151     
- Misses       2193     2436     +243     

Flag	Coverage Δ
integration	87.21% <100.00%> (-0.97%)	⬇️
unit	65.36% <50.00%> (-0.06%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
Unit Tests	65.36% <50.00%> (-0.06%)	⬇️
Integration Tests	87.21% <100.00%> (-0.97%)	⬇️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ash2shukla]

The failing integration tests are due to addition of a top level property config to macros which is missing from the corresponding json schema. This will get fixed once the corresponding changes are checked into fusion and jsonschema is synced.

[ash2shukla]

To keep the behaviour consistent with how its handled in exposures - see: #11589

[MichelleArk]

This should have no impact to state:modified given config is being newly introduced in this PR, and same_contents for macro resource only considers the macro sql:

dbt-core/core/dbt/contracts/graph/nodes.py

Lines 1186 to 1196 in 4deee3c

	class Macro(MacroResource, BaseNode):
	@classmethod
	def resource_class(cls) -> Type[MacroResource]:
	return MacroResource
	def same_contents(self, other: Optional["Macro"]) -> bool:
	if other is None:
	return False
	# the only thing that makes one macro different from another with the
	# same name/package is its content
	return self.macro_sql == other.macro_sql