Feature Request: Email notification about draft datasets

Overview of the Feature Request
This feature would enable an automatic reminder email to be sent to a deponent for any datasets left in draft status after a certain period of time (i.e. to remind them to either publish the draft, or submit for review, depending on the configuration of the particular installation). It would be ideal if the managers of a particular dataverse (e.g. institutional collection) could choose whether or not to turn this on, and at what time interval the reminders should be sent (e.g. 6 months, 12 months etc.).

The text in the email could reflect the already existing yellow banner that is displayed above draft datasets and hence say something like "Your dataset XX is still a draft version and is not yet published. Please revisit your dataset, and when you are ready to share, it either publish it or submit it for review. If you do not intend to publish this draft dataset, please delete it".

What kind of user is the feature intended for?
This would be a feature aimed at a depositor, but configurable by the manager of a particular collection.

What inspired the request?
We (at DataverseNO) have experienced that datasets are often left in draft status for a long time (presumably because the deponent started making a draft and then forgot about it, or they did not realise that they needed to press "submit for review").
There is a yellow banner above a draft dataset reminding the deponent of this, but they have no reminder when they come out of the system. Thus, a reminder email could be an effective way to get the deponent to log on to Dataverse again and deal with any lingering draft datasets. This suggestion actually came from a discussion of the issue on the Dataverse Users Community Google Group (from KU Leuven, as they have experienced similar issues).
See thread here: https://groups.google.com/g/dataverse-community/c/7jaVkOLpqFk

What existing behavior do you want changed?
We hope that this will remind deponents to take more responsibility for any draft datasets that they may have forgotten about, and hence make it less time consuming for collection managers to follow up about such datasets.

Any open or closed issues related to this feature request?
https://github.com/IQSS/dataverse/issues/7675 - This closed issue however, relates to in system reminders, whereas here we are talking about email (i.e. external) reminders.

The issue names no files, tests, or entry points to inspect. Clarify the configuration scope, reminder interval, recipient and email behavior before locating the notification and dataset-draft workflows; done means managers can configure the reminder and depositors receive it for qualifying drafts.