Send periodic email notifications to entity owner for attaching metadata forms

[LLY0203]

Is your idea related to a problem? Please describe.
Currently, when a new metadata form enforcement rule is created, owners of affected resources receive a one-time in-app notification informing them that they need to attach a metadata form to their resources.

However, if owners miss or accidentally clear this notification, there is no follow-up reminder. As a result, users may lose track of which resources still require metadata form attachments, leading to incomplete metadata compliance over time.

Describe the solution you'd like

1. Send a one-time email notification to the owners of affected entities when a new enforcement rule is created.
2. Set up a weekly ECS task to identify resources still missing mandatory metadata forms and send reminder emails to their owners.

P.S. Don't attach files. Please, prefer add code snippets directly in the message body.

[LLY0203]

Design Details

1. One-Time Email Notification on Enforcement Rule Creation

When a new metadata form enforcement rule is created, we already notify affected entity owners via the existing in-app mechanism using the function notify_owners_of_enforcement. I'm extending this by also sending a one-time email notification to the same set of owners. This is handled asynchronously via the existing worker queue system.

Within notify_owners_of_enforcement, after the in-app notification is added, we call another function notify_entity_owner_by_email to construct the email and submit a Task (with notificationType='email') to the queue. This task is picked up by the registered @Worker.handler('notification.service') and ultimately handled by SESEmailNotificationService.send_email_task(...).

Email template:

2. Weekly digest notification email

This workflow sends a weekly digest email to each user, summarizing all entities they own that are missing required metadata forms.

The implementation iterates over every metadata form and its associated enforcement rule, using _get_affected_entities(...) to collect all impacted resources. These are then aggregated into a map, structured as:

{
  user_email_id (str): {
    entity_uri (str): entity_object (dict with fields like name, type, owner, attached),
    ...
  },
  ...
}

Once the aggregation is complete, we iterate over the map and send a single digest email to each user using SESEmailNotificationService.send_email_task(...), listing their affected entities in one consolidated message. This digest is triggered by a scheduled ECS task that runs weekly.

By batching notifications, this format helps avoid spamming users with one email per entity and better aligns with our usability goals.

Email template:

[LLY0203]

Hi @petrkalos @SofiaSazonova @dlpzx — I’ve added the design details to this GitHub issue, as we discussed in yesterday’s review meeting. Feel free to take a look and share any feedback when you have a chance. Thanks again!

[LLY0203]

I've also submitted a PR based on this design for review. Appreciate your time reviewing it! #1838