[CT-3432] [spike] investigation - event system should completely control stdout

[nathaniel-may]

Is this your first time submitting a feature request?

• I have read the expectations for open source contributors
• I have searched the existing issues, and I could not find an existing issue for this feature
• I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature

Some dependencies of core and/or adapters do silly things like call print instead of using the python standard logger. This causes a bad experience for users who run with the --quiet flag, and for users who are trying to capture everything to a file. Details and examples can be found in this originating issue: dbt-labs/dbt-snowflake#847

Acceptance Criteria

• determine if this is possible, and if so what the possibilities are and what the implications are of each possibility

[graciegoheen]

Notes from technical refinement:

• we use print a lot for debugging, so we should make sure this still works in development
• how would we stop people from printing? there's other things (like system crash) we'd want to go to stdout
• this should be an investigation ticket to start, to see if there are any ways to achieve this
• more context in internal slack thread