Summary

This PR implements message status filtering functionality for the messages API, allowing users to filter messages by their processing status (PROCESSED, REMOVING, REMOVED).

Changes Made

Database Layer

• Added MessageStatusDb model to track message processing status and reception time
• Enhanced MessageDb model with one-to-one relationship to MessageStatusDb
• Optimized query performance using contains_eager with explicit joins for efficient status filtering

API Layer

• Added message_statuses query parameter (msgStatuses) to messages endpoints
• Updated default filtering to include PROCESSED and REMOVING statuses by default
• Enhanced message serialization to include status information in API responses

API Usage

GET /api/v0/messages?msgStatuses=PROCESSED,REMOVING
GET /api/v0/messages?msgStatuses=REMOVED

Testing

• Verify filtering works with single and multiple statuses
• Test API response includes correct status information
• Confirm query performance with large datasets

Breaking Changes

None - this is a backwards-compatible enhancement.