#1220 introduced nullness checks in the schema mapping inspection process. This generally reports all mismatches between the GraphQL schema nullness information and the corresponding Java type nullness.

We should refine this implementation with the following changes:

• if an application type is "non-null" and the GraphQL schema type is "nullable", we should not report that as a problem. Partial responses is a key GraphQL feature and we should not force developers to make fields "non-null" just because applications types are "non-null". If a data fetching error happens, the engine will null out fields in the hierarchy up until null is a valid value.
• use "errors" instead of "mismatches" as a consequence