Feature: Capture celery and kombu logs to a file

[stumpylog]

Proposed change

Not really a fix for #2787, but perhaps having the logs captured will allow further debugging or a better bug report to celery.

I also disabled gossip and mingle, which are only relevant if you're running multiple workers in a cluster to allow synchronization between workers.

Fixes # (issue)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other (please explain)

Checklist:

• I have read & agree with the contributing guidelines.
• If applicable, I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.
• If applicable, I have checked that all tests pass, see documentation.
• I have run all pre-commit hooks, see documentation.
• I have made corresponding changes to the documentation as needed.
• I have checked my modifications for any breaking changes.

[shamoon]

Celery stuff has the funniest names. Just thinking out loud (and not that it needs to be part of this PR) but wondering if we should include this log on the frontend

[stumpylog]

I guess their naming is green, healthy things? I'd never heard of kombu.

The logs could move to the frontend at some point. But it didn't look super interesting when just running normally

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns.