try to fix part of #4668

[wesleyking0]

To fully resolve the #4668 problem, it may require two steps:

• Skip resolving the @JsonTypeInfo annotation if a subtype is defined with @JsonTypeInfo and its definition is not compatible with the superclass.
• Confirming a more specific type during deserialization.

I have completed the first step, but I don't have a pretty good idea for the second step yet. -:)

[cowtowncoder]

I don't think I will be accepting this since usage on #4668 is wrong -- subtypes are not expected to change @JsonTypeInfo definition.

Put another way, @JsonTypeInfo definitions must be consistent across type hierarchy.