[dev] don't ignore GraphQL errors on watchQuery

[southerneer]

In the course of debugging issues with #3045 I stumbled onto a GraphQL problem. There were errors being generated on the server side that weren't making their way down to the client. Eventually I tried fiddling with the ApolloClient config in Transport.ts and discovered that we included errorPolicy: 'ignore'. I recall there was a good reason to do that at the time (maybe an extant bug in absinthe-socket?) but probably with the recent absinthe-socket update that setting needed to be reverted. Indeed when I commented out that config I was able to see the expected error message. We should also comment out the setting for watchQuery just in a separate PR with further testing to make sure it doesn't break anything.

[aksonov]

I guess it could be closed now

[southerneer]

We still ignore those errors (the line in Transport.ts changed though) so I'd still like to evaluate what happens when we don't ignore it.

[bengtan]

Not QA-able.