Fix #1654: @JsonDeserialize(contentUsing=...) ignored when resolving collection content type deserializer

[JacksonJang]

Issue: #1654
Reference: #5477

Thanks to your PR, I was able to resolve this issue easily!

Modified BasicDeserializerFactory.createCollectionDeserializer() to skip TypeDeserializer lookup when contentDeser (from contentUsing) is already specified:

TypeDeserializer contentTypeDeser = null;
if (contentDeser == null) {
    contentTypeDeser = (TypeDeserializer) contentType.getTypeHandler();
    if (contentTypeDeser == null) {
        contentTypeDeser = ctxt.findTypeDeserializer(contentType);
    }
}

This ensures that when a user explicitly specifies a custom content deserializer via @JsonDeserialize(contentUsing=...), the framework respects that choice and does not override it with type-based deserialization.

[JacksonJang]

I'll try again and submit a new PR.