Log every possible error and warning and improve error handling

[iamareebjamal]

The error reporting story of Open Event ecosystem is a sad state. In both server and frontend, generic errors are just caught and shown to the user who are presented with HTTP POST 409 https://akldjflksdfl... or An unexpected error occured. No one is none the wiser. Devs cannot tell what was wrong and what caused the system to error out because there are no logs on both frontend or server. Order was failed, but no logs. Discount code usage exceeded, but no logs. Tickets for event exhausted, but no logs

It is as if someone deliberately told devs to not use logging and error reporting in both frontend and server. Nothing gets logged, even on critical errors, and only unhandled errors are reported, because it is not possible to suppress them, or else I think they would be suppressed as well.

Goal is to:

• Log every possible error and even warning
• Reject pull requests if there is a generic catch block without logging
• Create a generic method which logs the error, parses it and shown proper error to user, at least what was sent from server, not just HTTP POST 409 https://akldjflksdfl... or An unexpected error occured
• Replace that generic error handler with specific user-friendly messages with all possible courses of action