Platform is overreacting if a wrong column name is queried

[zaychenko-sergei]

Open any dataset and run a custom SQL query referencing non-existing field.
The display of this very simple problem is a bit too loud:

It's clear that the API is failing with an internal error, so partially this has to be solved on the backend side.
After that, we need to verify a smooth display for this error type in UI.