[state:modified] store unrendered_database and unrendered_schema on source definition for state:modified comparisons

[MichelleArk]

Resolves #9573

Problem

source definitions in schema yaml files often include jinja in the database and schema properties.

However, this makes them sensitive to environment in that the env var/var/jinja resolution may change between runs without the actual source changing, leading to false positives.

Solution

Start persisting unrendered_database and unrendered_schema during source parsing, and do comparison on unrendered values during state:modified, behind state_modified_compare_more_unrendered_values behaviour flag.

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

All modified and coverable lines are covered by tests ✅

Project coverage is 89.17%. Comparing base (d1857b3) to head (1261b29).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #10675      +/-   ##
==========================================
+ Coverage   89.15%   89.17%   +0.01%     
==========================================
  Files         183      183              
  Lines       23344    23380      +36     
==========================================
+ Hits        20812    20848      +36     
  Misses       2532     2532              

Flag	Coverage Δ
integration	86.40% <100.00%> (+0.02%)	⬆️
unit	62.18% <67.56%> (+<0.01%)	⬆️

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

Components	Coverage Δ
Unit Tests	62.18% <67.56%> (+<0.01%)	⬆️
Integration Tests	86.40% <100.00%> (+0.02%)	⬆️

[MichelleArk]

Associated schemas.getdbt.com PR: dbt-labs/schemas.getdbt.com#63

[MichelleArk]

Sorry about the messy commit history, I think it's a GH issue from when the base was changed from #10487 to main. The changed files and contents all look correct though.