Structured Logging Cleanup

[nathaniel-may]

Describe the Feature

Now that the necessary items for 1.0.0 have been completed in #4260, we can continue working on these items.

Tasks

• revisit and cleanup add node_info to relevant logs #4336 Clean up node_status reporting #4370
• fine tune look and feel
  • respect user configs around color + printer width [Bug] dbt run with custom printer width #4373
  • handle duplication a la [ warn ] | [WARNING]: (less relevant now that log level are excluded from CLI)
  • handle text formatting RE this example.
• inspect every event to determine its destination(s)
• improve message wording (will break tests and that's ok. should rely on new codes from above instead)
• find a better alternative to extra.run_state and update the current tests that rely on that field. Tests are currently commented out.
• remove testing logs via Add "test" log level #3977
• better rpc backdoor that's not an env var dbt-rpc#63
• generated documentation from event dataclasses
• automated breaking change detection. (comparable static version schemas)
• json validation schema (better testing coverage, and potentially helpful with auto-detecting breaking changes)
• move deprecation message logic into the events module. Move this entry point higher up the list of functions.

[github-actions]

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please remove the stale label or comment on the issue, or it will be closed in 7 days.

[github-actions]

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.

[github-actions]

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.