[SE-4304] [SE-4495] feat: add celerybeat configuration

[gabor-boros]

The current implementation of celerybeat usage works properly if and
only if one concurrent worker process runs per queue using the nested
beat process started by the --beat flag. In case the the celerybeat
process is running as a separate process not as part of the workers,
that partially solves the problem. Either in that case, if multiple
instances are running in a cluster, without proper process supervising
across instances will result in (at least) dumplicated scheduling,
meaning that the scheduler will cause more work for the workers and
results will be duplicated.

Taking the above into consideration, to solve this issue, this commit
introduces single-beat package that wraps the celerybeat process and
keeps track of the process that acquired the lock in redis. In case one
of the instances get killed or the locking process crashes, the lock

refactor: use boolean flag to enable or disable celery beat
Co-authored-by: Joseph Mulloy jdmulloy@users.noreply.github.com

refactor: use boolean flag to enable or disable celery beat
Co-authored-by: Joseph Mulloy jdmulloy@users.noreply.github.com

Unindent a few entries that needd to be unindented (openedx-unsupported#6450) (openedx-unsupported#6467)
(cherry picked from commit 945fe9d)
Co-authored-by: Chris Pappas christopappas@users.noreply.github.com

[nizarmah]

👍

• I tested this by testing open-craft/openedx-platform#371.
• I made sure the cherry-picked commit mentions the commit is was cherry-picked from.
• I checked for accessibility issues
• Includes documentation