Define a standard way about how to forward errors to the user

[jonasraoni]

Source: #8724

Introduction

The system is composed by unexpected errors/exceptions, which are normally unhelpful (permission denied, out of disk space, etc.) or unsafe (any unnecessary exposure of backend details such as internal paths, credentials, etc.) to be shared directly with the end user.
There are also business logic exceptions, which are expected and safe to forward (e.g. only admins are allowed to delete).

Problem

At this moment we don't have a standard way to achieve that, so whenever it's needed, someone comes up with his own ideas.

Requirements/Ideas

• A kind of old pattern is to have a whitelisted class, from where you can inherit/generate user exceptions (e.g. throw new UserException('Your login has been disabled'))
• It should be possible to translate generic errors (e.g. I/O failure) into something useful for the user (e.g. "An unexpected error has happened, there's nothing you can do at this moment, the administrator has been notified and might get in touch with you soon")
• Some people like to think that "Exceptions/logs are made for administrators/developers/automated systems", and I think it makes sense. Some messages might come from external systems, OS, etc., and we won't be able to translate them anyway... If we follow this idea, we won't have the burden of translating every error message (which at this moment would lead to ##octorphes##).
• It's needed to have a way to group/react/filter a given type of error (e.g. DOI exceptions must be forwarded by email to the journal administrator, IO/database errors must be logged, etc.), because different types of messages have different types of requirements.

Other References

• https://laravel.com/docs/10.x/errors