Allow JsonbDeserializer based on generic types

[loicmathieu]

This PR allows to use the existing JsonbDeserializer not only based on a Class but also on a Type.
This allows to deals with Generic collections https://javaee.github.io/jsonb-spec/docs/user-guide.html#mapping-a-generic-collection

public class ListOfPersonDeserializer extends JsonbDeserializer {
    public ListOfPersonDeserializer() {
        super(new ArrayList<Person>(){}.getClass().getGenericSuperclass());
    }
} 

[gunnarmorling]

LGTM; shouldn't you be able to get away with a single field of type Type though (which Class implements)? Saving one field and the if/else upon deserialize.

[loicmathieu]

@gunnarmorling right but there is two different fromJson method on the JSONB interface so if I only use a Type field the fromJson(InputStream, Type) will be used in both cases.
As it's an interface, we cannot be sure that both impl will be the same.

[gunnarmorling]

Yes, theoretically, fromJson(InputStream, Class<?>) could do something different than fromJson(InputStream, Type) when receiving a Class. Yasson has the former call the latter, so it's exactly the same. But even if that were not the case, any fromJson(InputStream, Type) implementation should still do the right thing when being invoked for any subtype. So I'd go for that, but it's your call, I'm not hung up on it :)

[loicmathieu]

So I'd go for that, but it's your call, I'm not hung up on it :)

@gunnarmorling the simplier the better :)

I updated the PR accordingly

[loicmathieu]

@gsmet all native jobs failed, I let you relaunch CI when it's OK for you, hope it will be able to make it inside 1.2

[gsmet]

I rebased.