HTTP error responses from the API should not break Web Console rendering

Web Console makes certain assumptions about the error formatting (i.e. 400) coming from the HTTP API - i.e. tries to parse its content assuming they are JSON, etc. Further down the chain we are doing stuff like toLocaleString(), etc. which all can result in breaking in application render process (basically, a blank screen).

We should ensure that:

• We are rendering the associated error message only if a format matches the expected one and it's present at all
• Error position is set within range
• The logic prone to breaking happens is sufficiently isolated (i.e. in a try catch blocks) to prevent crashing the application.

Start by tracing the Web Console's HTTP API error-handling path into the application rendering process, using malformed or unexpected 400 responses to reproduce the blank screen. Done means mismatched or absent error formats do not render, error positions stay in range, and failures in the error-processing logic no longer crash the application.