Treat 422 http errors as graphql errors

[ins429]

I think 422 http errors should be treated as graphql errors. Right now if there's a 422 http error then it's treated as networkError, but instead we probably want it as graphQLErrors so the error can be gracefully handled.

Probably safe to check if the response has errors field to normalize the errors and move the operation forward.