Epic: Decouple API code sections

[SakuraIsayeki]

Problem:

Certains parts of a request's flow are not contingent for it's success or failure, and can be invoked in an auxiliary manner.
However, the current implementations consider them as integral parts of the flow, meaning that any failure in these auxiliary components (e.g: Notifications) will result in a request failure, even if the essential elements of a request were fullfilled.

Objective:

These code sections should be switched to event-driven executions, triggered before/after a request's essential flow is invoked.

One easy way to implement this would be through the use of Hangfire, which allows for job triggering, in a fire-and-forget style. Further expanding on this conjecture, more parts of the code could rely on this approach for heuristic-based executions (e.g: database trimming, etc).

Workload

• Modularize notifications output for Discord Webhooks #105