Fix #4629: Handle conflicting creatorProp + ignore conflict (Kotlin data class compatibility)

[JacksonJang]

I resolved #5433

[cowtowncoder]

Ok so my problem here is the double lookups in every case, even if in most cases single lookup (for CreatorProperty) should be necessary.
Now, in theory, _propNameMatcher lookup should be enough (matcher should be superset of ALL SettableBeanProperty entries, and type of property could be checked separately, as needed.

I am trying concurrent changes to do that, but having some problems. Alternatively this PR could be refactored to limit need for extra lookups I think.

[JacksonJang]

Thank you for the answer :)
I’ll review that part of the code as well and try refactoring it.
Once I make the improvements, I’ll update the PR.

[cowtowncoder]

@JacksonJang Can we actually reproduce the issue with plain Java? It'd be very useful to have test here instead of requiring Kotlin module's test.

[JacksonJang]

Okay.
I’ll work on creating a plain Java test case that reproduces the issue.

[cowtowncoder]

One thing I noticed is that in Java @JsonIgnore cannot be added to constructor parameter, so need to probably use a custom AnnotationIntrospector to fake it (not sure if/why/how Kotlin allows).
Or alternatively maybe @JsonIgnore is only added on backing Field, then, in Kotlin class.