[Draft] add Optional node_color config in Docs dataclass

[matt-winkler]

related to #5255

Description

Adds a configuration to allow custom node_color config in a docs block.

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.

[matt-winkler]

Open questions:

• Does this create a need to set default color configurations by node type? E.g. macros, seeds, tests, etc.

• This will be just for models

• Any impact from partial parsing behavior? From testing locally, I found that setting a default value in the Optional config block created mass changes to all node types

• Identify any issues here from testing

• Will this work with DAG-in-IDE for cloud?

• Yes

[matt-winkler]

@b-per You mentioned starting to take a stab at this. This update appears to work for setting a default docs dictionary within config.

However, when setting this from the dbt_project.yml, it only works when including the + syntax on the docs property. Otherwise, I get an unused configuration paths error. I'm missing something with how those properties from the project are parsed - can you help me out?

[b-per]

I have also created #5397 with docs configurable in dbt_project.yml.

@matt-winkler I am not 100% sure why the + is required before docs is a dictionary (this page mentions that this is the same for persist_docs)

[jtcohen6]

Closing in favor of #5397 :)