feat: add logging of latency to both error and success messages

[kribor]

No description provided.

[kribor]

Change of order for consistency with error message and ease of parsing

[kirillgroshkov]

So, you're proposing to make 2 changes:

1. change the order of the log message on response

2. change the err.message to include the latency information

Number 2 is user-facing, BTW, so it'll be a change in what users see in the Frontends (among other places).

My quick feedback is that, while the changes are not so significant at the first look, in my head the motivation of the change doesn't align with the change itself. E.g "because we want the message to be better parse-able - I'd like to change how we log it".
I want to argue that these plain text messages are not intended for the automatic consumption/parsing in the first place, we might use structured logging for these cases instead.

So, I want to open a slack discussion and propose another solution, such as a hook, that would allow for structured logging that is independent of "default/user-facing logging".