Schema inspection does not catch argument name mismatch

[OleBilleAtBS]

Hi Fellas

Just enabled the schema inspection from #386 and I have a suggestion for additional validation it could make. If the arguments have different names then the ones provided in the schema theyre not mapped when the query is triggered.

Example.

My graphql file.

type Event {
  id: ID!
  name: String!
  description: String
  location: String
}

type Query {
    allEvents(
        first: Int
    ): [Event]
}

My java query resolver

@Controller
@Component
public class EventsQueries {
  @QueryMapping
  public List<Event> allEvents(@Argument Integer anotherName) {
    List<Event> results = new ArrayList<>();
    results.add(new Event(1, "name", "Desc", "Loc"));
    return results;
  }
}

The report looks like this

2023-08-29T14:07:46.959+02:00  INFO 76304 --- [           main] c.e.g.config.GraphQlConfiguration        : GraphQL schema inspection:
	Unmapped fields: {}
	Unmapped registrations: {}
	Skipped types: []

If i trigger a query like this

query {
  allEvents(first:1) {
    id
    name
  }
}

then the "anotherName" value is null. It would be nice if the schema inspection could warn about it.

[rstoyanchev]

Indeed, currently we don't check arguments and input types, but we could.

[rstoyanchev]

This should be covered by #740.