feat: inline chores notifications

[thisislawatts]

This branch integrates chore notification functionality that was previously hosted within the Aggregator, into this CRM application. The intention of the migration is to avoid making significant changes to the logic. The changes to the CRM include:

Core Functionality Added:

• Event Generation: Support for both recurrent (cron-based) and single-occurrence chore events
• Notification System: Email-based reminder system for volunteers with duplicate prevention
• Management Command: send_reminders command for processing scheduled notifications. This can be invoked by a cron job to trigger the reminders.

Key Architectural Change:

• Database-backed Notification Tracking: Introduced ChoreNotification model to replace Redis-based duplicate prevention from the previous implementation. This provides persistent storage and better integration with Django's ORM.

Key Components:

• chores/core.py (417 lines): Core logic for chore events, time calculations, and notification processing
• chores/models.py: Database models for chores, volunteers, and notification tracking
• chores/management/commands/send_reminders.py: Django management command for sending reminders
• chores/messages.py: Email message templates for volunteer reminders

Dependencies Added:

• croniter>=6.0.0 - from aggregator for cron-based scheduling
• humanize>=4.12.3 - from aggregator for human-readable time formatting
• time-machine>=2.16.0 - For time manipulation in tests
• factory-boy>=3.3.3 - For test data generation

Minor Changes:

• Added full_name property to User model in members/models.py
• Comprehensive test suite with factories and model tests

Impact:

This consolidation eliminates the need for a separate service while maintaining the same functionality for chore scheduling and volunteer notification management. The system supports complex scheduling patterns and prevents duplicate notifications through database tracking instead of Redis, providing better persistence and integration with the Django ecosystem.

This PR introduces the logic, but it will need to be tied into a cron job on the server before it is functional.

Supporting diagrams:

Current implementation in Aggregator

New implementation

[thisislawatts]

Note Commits will be squashed prior to merge