Confusing usage of InvariantViolation error #123
Description
There some confusing usage of GraphQL\Error\InvariantViolation error in the lib, sometime this error is use to send some useful information to graphQL clients (wrong types value parsing like here) and sometime we use it to send system error (sensitive information) that should not be display to client (here an example). Can we separate both information throw two distinct exception? This we help to create a more safe prod environment without hiding useful errors to client...