[Platform] [User Notifications][TUS] Notifications are available and read-only within logged-in user context

[becevka]

Summary
In order to support User Notifications, we need to assign them to the user and prevent unauthorized access to notification data.

Describe the solution you'd like
Notifications Collection should consist of the following fields:

• event, reference to Event Collection
• user, reference to the user subscribed to Business Entity
• createdDateTime, date when event was created
• readDateTime, date when event was marked as read and switched to be inactive

Notifications endpoint should allow only read notifications for the currently logged in user (utilizing Strapi Policies).
Notifications endpoint should not allow any modifications to notifications.
Notifications endpoint should allow to filter notifications by createdDateTime and readDateTime fields.

Acceptance Criteria

Generated by Zenhub AI

• Scenario: Notifications are assigned to the user
  • Given a user is logged in
  • When a notification is created
  • Then the notification should have a reference to the user
• Scenario: Notifications endpoint only allows read access for the logged-in user
  • Given a user is logged in
  • When the user requests their notifications
  • Then the user should only be able to read their notifications
• Scenario: Notifications endpoint does not allow modifications to notifications
  • Given a user is logged in
  • When the user attempts to modify their notifications
  • Then the user should receive an error or be unable to make changes
• Scenario: Notifications endpoint allows filtering by createdDateTime and readDateTime fields
  • Given a user is logged in
  • When the user filters their notifications by createDate and active fields
  • Then the user should receive a filtered list of notifications based on the specified criteria

[becevka]

@oriyomibadmus

• Please add a user to existing Notification to experiment with strapi Policies.