feat: emails sent table migration

[kwasniew]

About the changes

Background: we need to send emails for productivity report every month. We need to guarantee at most once delivery semantics.

Solution: Create sent_emails table. There's a potential vector of change that involves more email types so I optimize for this use case.

Proposed structure:

• id is similar to trends ids YYYY-MM and indicates that we have already sent a report for 2024-10
• type is the email type and it accommodates different email types
• created_at is the exact date we sent out the email (useful for tracking if we sent out emails when we intend)
• payload - so that we know what dynamic data was provided in the template (it allows re-sent capability in future and debugging)

Note: this PR will be merged once we used it in sample code that gives us feedback that the structure is solid.

Important files

Discussion points

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
unleash-monorepo-frontend	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 25, 2024 7:50am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
unleash-docs	⬜️ Ignored (Inspect)	Visit Preview		Oct 25, 2024 7:50am

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details

Scanned Manifest Files