Add notification preference handling for chat and group posts

[tenkus47]

• Integrated user notification preferences into chat and group post notification services, allowing for more granular control over notifications based on user settings.
• Implemented functions to filter users by their notification preferences, ensuring that only eligible users receive notifications.
• Updated relevant services and repositories to accommodate the new notification preference logic, enhancing the overall notification system.
• Added tests to verify the correct behavior of the new notification preference features, ensuring robustness and reliability.

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge.

Summary

• Adds the preference schema, migration, API endpoints, models, repository, and service.
• Applies preference filtering to chat, group-post, event, event-reminder, and series-reminder recipients.
• Adds regression coverage for preference resolution, duplicate updates, and notification filtering.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[Preference API] --> B[Preference service]
  B --> C[(User notification preferences)]
  D[Notification dispatch] --> E[Recipient query]
  C --> E
  E --> F[Eligible recipients]
  F --> G[Push delivery]

Loading

[greptile-apps]

Exposed toggles remain unenforced

When a user disables or mutes EVENT_REMINDER, ACCUMULATION, or SERIES, the API persists and returns that setting, but the corresponding dispatch paths never consult these preferences. Notifications of those types therefore continue to be delivered despite the reported setting.

Prompt To Fix With AI

This is a comment left during a code review.
Path: pecha_api/notification/notification_preference_enums.py
Line: 68-71

Comment:
**Exposed toggles remain unenforced**

When a user disables or mutes `EVENT_REMINDER`, `ACCUMULATION`, or `SERIES`, the API persists and returns that setting, but the corresponding dispatch paths never consult these preferences. Notifications of those types therefore continue to be delivered despite the reported setting.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

[sonarqubecloud]

Quality Gate passed

Issues
19 New issues
0 Accepted issues

Measures
0 Security Hotspots
84.5% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud