[CT-1658] Logging changes break dbt-rpc

[peterallenwebb]

Is this a new bug in dbt-core?

• I believe this is a new bug in dbt-core
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

Due to recent changes, logs are now written to the logbook GLOBAL_LOGGER using the same numeric priority as used for native Python logs, but they are not compatible. Furthermore, the GLOBAL_LOGGER is not written to by default, and dbt-rpc does not do its own log set up. We need to correct both issues so that dbt-core logging behavior with respect to the legacy logbook code remains the same in 1.4 as it was in 1.3.

Expected Behavior

When DBT_ENABLE_LEGACY_LOGGING is true, dbt-core should exhibit the same log output behaviors as it did in 1.3.

Steps To Reproduce

The issue can be seen in the GitHub actions for the dbt-rpc build, which are currently failing.