[state:modified] persist unrendered_config from schema.yml, and more reliably compute unrendered_config from .sql files

[MichelleArk]

Resolves #9564

Problem

1. A node's unrendered_config included rendered values, because the population of unrendered_config from models with config in .sql files was occurring after kwargs were evaluated by value (e.g. materialized=(jinja expression) => jinja expression evaluated by the time we are in ConfigProviders)

2. We were not storing the unrendered_configs from schema.yml parsing

Solution

All behind the new behaviour flag, state_modified_compare_more_unrendered_values

1. Parse the unrendered_config on the node from .sql from the raw model code and store values as string representations of jinja calls
   • multiple config calls are merged naively, since we only have string types in the values
2. Store unrendered_config on the schema file under manifest.file
   • storage under schema.yml key (e.g. "models") -> name (versioned names have _v{version} suffixes
3. During node parsing, look up the unrendered_configs from the schema file and use them as the patch_config_dict

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.

[codecov]

Codecov Report

Attention: Patch coverage is 95.95960% with 4 lines in your changes missing coverage. Please review.

Project coverage is 89.09%. Comparing base (1fd4d2e) to head (5b0bce0).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #10487      +/-   ##
==========================================
+ Coverage   89.03%   89.09%   +0.06%     
==========================================
  Files         182      182              
  Lines       23195    23288      +93     
==========================================
+ Hits        20651    20748      +97     
+ Misses       2544     2540       -4     

Flag	Coverage Δ
integration	86.31% <95.95%> (+0.07%)	⬆️
unit	62.22% <69.69%> (+0.03%)	⬆️

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

Components	Coverage Δ
Unit Tests	62.22% <69.69%> (+0.03%)	⬆️
Integration Tests	86.31% <95.95%> (+0.07%)	⬆️

[MichelleArk]

Corresponding schemas PR: dbt-labs/schemas.getdbt.com#60

[MichelleArk]

even though this isn't serialized, we still need a schemas.getdbt.com PR, similar to config_call_dict: dbt-labs/schemas.getdbt.com#60

[gshank]

It would be really nice to spend some time making all the config application and merging code cleaner. Maybe next quarter...