perf: init loggers once

[beckermr]

Description

This PR initializes the loggers once at the top of each module to hopefully reduce overheads.

Checklist - did you ...

• Add a file to the news directory (using the template) for the next release's release notes?
• Add / update necessary tests?
• Add / update outdated documentation?

closes #5382

[beckermr]

@conda/builds-tools This PR is ready for review!

Note that the python 3.12 failures are due to a deprecation warning for python 3.14 that comes out of code in conda-package-handling.

[dholth]

How much do we understand about the original behavior, besides that conad-build does strange things to logging (store all messages and suppress duplicates?) as a side effect of importing its logging utility? There was a comment about the user being able to override settings?

[beckermr]

I understand nothing and yes user overrides are really hard.

FWIW, the current code base has a mix of making the loggers once at the top of each module versus making them on-the-fly. This PR simply changes all of the loggers to be made at the top of each module. So apparently the loggers do work when imported at the top. I'd like to defer cleaning up and/or changing the logging usage to another PR.

[codspeed-hq]

CodSpeed Performance Report

Merging #5383 will not alter performance

_{Comparing beckermr:init-logger-once (5674c02) with main (ee7d0ce)}

Summary

✅ 3 untouched benchmarks

[beckermr]

I am closing this in favor of a smaller fix in #5384.