Celery Logging Update

[corlettb]

https://trello.com/c/btX99C0D/1085-celery-workers-not-logging-critical-errors

What

• Remove the warnings override. Feels a bit dodgy. It only means we miss a few items on startup
• Allow celery beat and celery worker log levels to be specified independently and from our normal config setup.
• Update tests to include celery beat log tests
• Add test to ensure we do not print celery worker log messages if log level is CRITICAL.

Why

Previous implementation lacked beat testing and was using a non-standard configuration

[risicle]

Add test to ensure we do not print celery worker log messages if log level is CRITICAL

I thought CRITICAL were the ones we did want 😕

[risicle]

I thought CRITICAL were the ones we did want 😕

Or perhaps by "worker logs" you meant the boring, lower-level worker logs, which indeed we don't want.

[corlettb]

I thought CRITICAL were the ones we did want 😕

Or perhaps by "worker logs" you meant the boring, lower-level worker logs, which indeed we don't want.

I added the test to ensure we don't print any non-critical messages if CRITICAL has been specified as the log level. As we know the celery worker logs can leak PII I just wanted a double check to ensure the logic is correct.