Return better GraphQL errors in development

With us ramping up in GraphQL I'd like to improve the development experience, especially request specs.

When developing functionality in GraphQL, there is often a '500 internal server error' which doesn't give much else in terms of errors. I'd like to see a more robust error returned on development to aid in debugging and to speed up development.

This may be solved concurrently with #205392 (closed).