UNRESOLVABLE_SCHEMA and other warnings should not lead to unexpected behavior. #386
Description
At least for the UNRESOLVABLE_SCHEMA warning, which has the mitigation "Ignore and continue. May lead to unexpected behavior." is alarming. It seems to me that in a case where a schema cannot be resolved, then it should instead use the arbitrary JSON type.
Related to discussion related in #330 where we discuss moving the allOf and oneOf resolution logic into the getSchemaTargetGraphQLType