refactor: call transformError when error is thrown outside of actions

[lionelhorn]

Summary of changes

• Previously transformError was not called when an error occured in kernel.authenticate() for instance
• Enable better sanitization of errors

Relinquishment of Rights

Please mark following checkbox to confirm that you relinquish all rights of your changes:

• I waive and relinquish all rights regarding this changes (including code, text, and images) to Deepkit UG (limited), Germany. This changes (including code, text, and images) are under MIT license without name attribution, copyright notice, and permission notice requirement.

[marcj]

this does not include errors that are nominally thrown like these (since it early exits at line 730)

@entity.name('@error:user')
class UserNotFound extends Error{}

while looking at that code I really wonder if we get then even a good stack trace at all even within the client. it seems the new e.stack = '' and the old e.stack = error.stack ... just drops all the information, which is not good. we likely want to maintain the actual stack trace on the client side so users see in what code the error was thrown