Use configured Celery concurrency values instead of hardcoded values (#3403)

[iGufrankhan]

Fixes #3403

Description

This PR replaces the hardcoded Celery worker concurrency values in
augur/application/cli/tasks.py with the configurable values defined in the Celery section of the Augur config.

The following settings are now read dynamically through AugurConfig:

• core_worker_count
• secondary_worker_count

The scheduling worker intentionally remains at --concurrency=1, since only one scheduler should run at a time.

Notes for Reviewers

• No functional behavior is changed besides making concurrency configuration-driven.

Signed commits

• [x] Yes, I signed my commits.

[MoralCode]

The process names is separate. this PR updates the CLI to use the values from the config (augur.json or DB) for concurrency values when starting aufur from CLI

[sgoggins]

The process names is separate. this PR updates the CLI to use the values from the config (augur.json or DB) for concurrency values when starting aufur from CLI

ok ... with that and the redundant tag I'm unsure what to do with this one ...

[MoralCode]

The process names is separate. this PR updates the CLI to use the values from the config (augur.json or DB) for concurrency values when starting aufur from CLI

ok ... with that and the redundant tag I'm unsure what to do with this one ...

Redundant tag just serves as a flag to say "hey, there are duplicates of this thing" (i.e. if two newcomers submit PRs for the same issue). it just means we have to make sure we pick the PR with the best implementation and, once it merges, the other one gets automatically closed for being a duplicate.