InvalidNullError not showing up in GraphQL::Client::Response errors since Graphql-ruby 2.4.11

I'm trying to upgrade our version of graphql gem from 2.4.10 to 2.4.11, and this [commit](https://github.com/rmosolgo/graphql-ruby/commit/b74c41baaad24668b28ec47a3002c3864a717dc7) changes default InvalidNullError handling.
Because of that change, all of a sudden my response object doesn't have the errors populated within the errors attribute (see example).

Before:
```Ruby
#::Mutation labelCreate=nil>,
@errors=
#["Cannot return null for non-nullable field LabelCreatePayload.errors"]} @details={"data"=>[{"message"=>"Cannot return null for non-nullable field LabelCreatePayload.errors", "normalizedPath"=>["data"]}]}>,
@extensions=nil,
@full_response=nil,
@original_hash=
{:http_status=>"200",
"errors"=>[{"message"=>"Cannot return null for non-nullable field LabelCreatePayload.errors"}],
"data"=>{"labelCreate"=>nil}}>
```

Now:
```Ruby
=> #::Mutation labelCreate=nil>,
@errors=#,
@extensions=nil,
@full_response=nil,
@original_hash=
{:http_status=>"200",
"errors"=>[{"message"=>"Cannot return null for non-nullable field LabelCreatePayload.errors", "locations"=>[{"line"=>3, "column"=>5}], "path"=>["labelCreate", "errors"]}],
"data"=>{"labelCreate"=>nil}}>
```

Is this normal? Could I get some help understanding why that may be happening?

Beginne damit, das Verhalten von GraphQL::Client::Response zwischen graphql 2.4.10 und 2.4.11 zu vergleichen, und verwende dabei den verlinkten Commit sowie die Vorher-/Nachher-Response-Beispiele in diesem Issue. Verfolge anschließend, wie InvalidNullError und das errors-Attribut der Response behandelt werden, und ermittle dann, ob das Verhalten von 2.4.11 erwartet ist, und erkläre die Ursache oder die erforderliche Änderung.

Vom Indexierungsmodell aus dem Issue-Text verfasst.