GraphQlWebSocketHandler incorrectly turns ExecutionResult with errors into an "error" message

[rstoyanchev]

Currently if the ExecutionResult for a single response operation (query or mutation) is turned into an "error" message. However, according to the spec, an "error" relates to issues before request execution:

Operation execution error(s) triggered by the Next message happening before the actual execution, usually due to validation errors.