Rethink logging setup in conda and conda-build

[jaimergp]

Checklist

• I added a descriptive title
• I searched open issues and couldn't find a duplicate

What?

Rethink how we use logging in conda and conda-build.

Why?

Conda and conda-build’s logging setups are too complex. It has caused muddy logs in conda-build for years, it’s behind performance problems in conda, and floods the logs of the test suite in each run.

User impact

• Application users won't suffer performance issues from excessive logging
• conda-build logs will look cleaner
• library users won't have to deal with the complexities built in conda's logging system

Goals

• More idiomatic usage of logging, with few or no hacks.
• Rethink which logging handlers are needed
• Make sure the handlers are only enabled on the application layer
• Document and audit which levels should be used for which kind of messages

Tasks

• Stop using log.trace(...) #13732
• Debug code guarded with log.isEnabledFor(logging.DEBUG) is always run #13541
• Improve logging #13735
• Pip install logs not shown with verbose option. #10556
• add rolling file log #7352 (reopen?)
• unexpected urllib3 DEBUG logging from conda-build conda-build#4539 fixed by delay imports in command plugin conda-build#4953 but I don't know why
• Improve error logging on each step of the build process  conda-build#683 (reopen?)
• Optional structured logging for running conda build in CI conda-build#4846
• Logging info being printed conda-build#2106
• Limit logging config to CLI conda-build#5274

This epic is blocked by:

N/A

This epic blocks:

Not a blocker, but it does interact with #13707