[Feature] Notification delivery throttling timeout

[joaquinco]

Introduction

Allow users to specify a timeout for notification deliveries that are hold off by some notification_trigger counting strategy.

Changes

• Refactor code that gets generated by using BoomNotifier module by just defining wrapper functions of the notify_error related logic (now in BoomNotifier.Api) with a specific configuration.
• Refactor code so that notification triggering is decided in the NotificationSender (ex NotifierSenderServer) GenServer. So we can handle the timeout in the same process.
• Change tests that used self() to send messages back and forth test examples to named process.
• Save the error info hash key in the ErrorInfo struct
• Unify Faker Mailers

[germanbottosur]

I've been taking a look at the code in general and I think looks good overall 🙌

Apart from that, I think we should take a look at the String.to_existing_atom/1 thing and to the way we retrieve the error occurrences when resetting the accumulated errors. I still have to take a closer look at the NotificationSender but I suspect we may introduce a race condition if we don't retrieve the occurrences and reset the accumulated errors in an atomic step for the ErrorStorage agent (let's say that some other process is storing a new error occurrence while the sender is resetting it).

I'll be taking a deep look at the notification sender process later and I've left some suggestions to try to keep a consistent use of the pipe operator.

Great work 🙌

[iaguirre88]

@joaquinco Thanks for taking your time for implementing this 🚀
It's looking great 🤘

[iaguirre88]

I'm gonna let you @germanbottosur do the approval since you've been working more closely on this 💖

[germanbottosur]

🙌