Detect changes to model access, deprecation_date, and latest_version in state:modified

[MichelleArk]

resolves #8189
docs dbt-labs/docs.getdbt.com/# dbt-labs/docs.getdbt.com#3897

Problem

Solution

state:modified picks up changes to a model's ref representation:

• modifying access
• modifying deprecation_date
• modifying latest_version

Any of these may cause downstream ref calls to change: potential errors from changing access, a different resolution of unpinned refs when latest_version changes, or additional warnings from deprecation_date.

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/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

[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

Merging #8264 (8e171b8) into main (f230e41) will increase coverage by 0.01%.
Report is 9 commits behind head on main.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #8264      +/-   ##
==========================================
+ Coverage   86.22%   86.24%   +0.01%     
==========================================
  Files         174      174              
  Lines       25515    25522       +7     
==========================================
+ Hits        22001    22011      +10     
+ Misses       3514     3511       -3     

Files Changed	Coverage Δ
core/dbt/contracts/graph/nodes.py	94.49% <100.00%> (+0.02%)	⬆️
core/dbt/node_types.py	98.03% <100.00%> (ø)

... and 11 files with indirect coverage changes