Allow custom HandlerMethodArgumentResolvers to override built-ins

[trehak1]

We have DTOs shared across Graphql and REST, using JSON, with constructors like this:

    @JsonCreator
    public Extension(@Nonnull @JsonProperty("userId") UUID userId,
                     @Nonnull @JsonProperty("extensionName") String extensionName,
                     @Nonnull @JsonProperty("isBase64Encoded") Boolean base64,
                     @Nonnull @JsonProperty("extension") String extension) {
        this.userId = userId;
        this.extensionName = extensionName;
        this.base64 = base64;
        this.extension = extension;
    }

I'd love to use my custom HandlerMethodArgumentResolver as now supported in main.
However, custom argument resolvers comes LAST, therefore code using the input object described above fails on exception while default binder is trying to deserialize it using constructor deserializer.

[rstoyanchev]

This is for an @Argument method parameter? Currently GraphQlArgumentBinder does not expose object creation. That's what #521 aims to do. So will your custom argument resolver replace the one for @Argument completely? In which case, a custom annotation, e.g. @JsonArgument makes sense, and built-in resolvers will not interfere.

Generally in Spring MVC and elsewhere we order custom resolvers after the built-in ones, and instead of replacing them completely, we try to provide the necessary control over their behavior. That way the built-in method parameters have a predictable, well-known behavior, and if that doesn't work for you, then you can create your own, but keeping that separate in the programming model.

[trehak1]

Sure, #521 is a way to go.