fix(#57): Remove unused Celery configuration and dependencies

[Amarjeet325]

…Quantara environment resolves #57

Problem
The docker-compose.quantara.yaml file was referencing a nonexistent quantara_tracker.celery_config module for its celery and celery_beat services. This caused the background workers to fail on startup. Since a codebase audit confirmed that Celery tasks are not actively used anywhere in the application, the missing configuration is not needed.

Solution
Opted to cleanly remove all unused Celery infrastructure rather than adding dummy configuration modules.

Changes Made:

• Removed celery and celery_beat background services from devops/docker-compose.quantara.yaml.
• Removed the redis service and its associated volume redis_data from devops/docker-compose.quantara.yaml as it was only utilized by the removed Celery workers.
• Removed celery and redis Python dependencies from quantara/pyproject.toml.
• Verified that back.yaml and dev.yaml have no residual references to Celery.

Testing:

• Verified that Docker Compose starts cleanly without attempting to launch broken background tasks.

[YaronZaki]

Good cleanup — since Celery isn't being used, removing it (and the dead docker-compose services and pyproject deps) is cleaner than patching the broken config. Approving and merging.

[YaronZaki]

Heads up — the recent merges into main have introduced a small conflict in your branch (quantara/frontend/package.json + yarn.lock). The Celery removal itself in the Python side is fine, no conflict there. Could you rebase on main and push? I’ll merge right after.

[YaronZaki]

Hey @Amarjeet325 👋 Love the cleanup! Removing the dead Celery/Redis config is exactly what #57 was asking for, and pruning the lock files alongside it is the right call. The branch has a merge conflict against main now though — could you rebase and update? Already approved in principle, just needs a clean merge. Thanks! 🎯

[Amarjeet325]

Hey @YaronZaki I have resolved the conflicts; please review and merge it.