feat(nestjs): Add SentryGlobalGraphQLFilter

[nicohrubec]

BaseExceptionFilter should not be used in GraphQL applications (ref). Currently the SentryGlobalFilter extends the BaseExceptionFilter, which is why GraphQL applications break if an exception is thrown.

By default, NestJS + GraphQL environments use the ExternalExceptionFilter (ref), which essentially just rethrows the error. So I added a new SentryGlobalGraphQLFilter that captures the exception in Sentry and then simply rethrows the error.

Additionally, added a new e2e test app to test GraphQL applications. Added a test to verify that basic error reporting works correctly now.

[lforst]

I just noticed this but let's remove the static keyword from this field. Also in all the other places where we have it. We are not using it in a static way and defining a static in JS is considered a side-effect and that becomes problematic in some scenarios. (it inhibits tree shaking for example)

[lforst]

m: I am a bit sus because we identified previously for HTTP contexts taht throwing in error filters will not make the behaviour transparent. Is this the case for graphql?

[nicohrubec]

Seems to be fine, the response from the test error endpoint looks like this:

{
  errors: [
    {
      message: 'This is an exception!',
      locations: [Array],
      path: [Array],
      extensions: [Object]
    }
  ],
  data: null
}

[lforst]

Did you check what the server returns before/after you added the filter? We need to be careful not to modify any responses.

[nicohrubec]

Yes, responses are the same with/without filter. I also now added the logging logic from the ExtenalExceptionFilter so now output also aligns perfectly.