MNTOR-3919: cronjob WIP for churn emails

[mansaj]

References:

Jira: MNTOR-3919

Description

Cronjob for sending out emails

Checklist (Definition of Done)

• Commits in this PR are minimal and have descriptive commit messages.
• I've added or updated the relevant sections in readme and/or code comments
• I've added a unit test to test for potential regressions of this bug.
• If this PR implements a feature flag or experimentation, the Ship Behind Feature Flag status in Jira has been set
• Product Owner accepted the User Story (demo of functionality completed) or waived the privilege.
• All acceptance criteria are met.
• Jira ticket has been updated (if needed) to match changes made during the development process.
• Jira ticket has been updated (if needed) with suggestions for QA when this PR is deployed to stage.

[mansaj]

this part is still TBD, I'm looking into perhaps a different way of getting the data in

[mansaj]

The rendering of the email part will go here @Vinnl

[github-actions]

Preview URL 🚀 : https://blurts-server-pr-5495-mgjlpikfea-uk.a.run.app

[rhelmer]

lgtm at a high level - I guess we'd need to remove the unused imports and finalize the way we're getting this data. @mansaj is there any point to storing this in our DB or caching it etc. or are you planning to just read it and move on? Any concern about duplicates (I assume we keep track of who we emailed this to and don't resend)?

[mansaj]

lgtm at a high level - I guess we'd need to remove the unused imports and finalize the way we're getting this data. @mansaj is there any point to storing this in our DB or caching it etc. or are you planning to just read it and move on? Any concern about duplicates (I assume we keep track of who we emailed this to and don't resend)?

ideally we don't store at all.
There is a new field I added with the previous PRs to address the dup check, there's a section in this PR to check for dups in the script