Respect worker log level config setting

[soapy1]

Description

This small PR updates the conda store worker to respect the CondaStoreWorker.log_level config parameter. Now users can see that the log level set for their works gets applied to the worker.

Pull request checklist

• Did you test this change locally?
• Did you update the documentation (if required)?
• Did you add/update relevant tests for this change (if required)?

How to test

Before this change, the worker was always running at logger.INFO log level. For example, you can see in the log output

. . .
conda-store-worker-1  | [2024-10-19 01:41:55,960: INFO/MainProcess] Connected to redis://:**@redis:6379/0
conda-store-worker-1  | [2024-10-19 01:41:55,962: WARNING/MainProcess] /opt/conda/envs/conda-store-server/lib/python3.12/site-packages/celery/worker/consumer/consumer.py:508: CPendingDeprecationWarning: The broker_connection_retry configuration setting will no longer determine

To test this add the following line to your conda-store config file

c.CondaStoreWorker.log_level = logging.ERROR

Restart the server and view the logs. Notice that the WARN and INFO log lines no longer appear in the logs.

[netlify]

✅ Deploy Preview for conda-store canceled.

Name	Link
🔨 Latest commit	a752f6d
🔍 Latest deploy log	https://app.netlify.com/sites/conda-store/deploys/671310639769830008fe9f84

[netlify]

✅ Deploy Preview for conda-store canceled.

Name	Link
🔨 Latest commit	04fe23a
🔍 Latest deploy log	https://app.netlify.com/sites/conda-store/deploys/67166ab97f126100083bd23e

[soapy1]

There isn't really a 1:1 relationship between the logging package error levels and the expected logging levels for celery. So, I think maintaining a map is required. Definitely open to suggestions if there is a better place to put this, like maybe a utils type file that I missed.

[peytondmurray]

This definitely looks correct, but given that Nebari may be impacted I'm going to wait for the okay from Nebari devs before merging this.

[peytondmurray]

Confirmed after talking with @viniciusdc that this should be safe to do. Thanks!