Cleanup Jackson type info mess fixes (#9441)

[rpost]

Cleanup as mentioned in #9441

Mentioning Java and JavaSpring committee:

@bbdouglas @sreeshas @jfiala @lukoyanov @cbornet @jeff9finger @karismann @Zomzog @lwlee2608

@cachescrubber @welshm @MelleD @atextor @manedev79 @javisst @borsch @banlevente

[borsch]

LGTM

[cachescrubber]

I have no time yet to dig into this - but just based on the title i guess this will affect

#11650

please keep that in Mind.

[rpost]

I have no time yet to dig into this - but just based on the title i guess this will affect

#11650

please keep that in Mind.

do you want me to somehow respond to this?

[welshm]

I have no time yet to dig into this - but just based on the title i guess this will affect
#11650
please keep that in Mind.

do you want me to somehow respond to this?

Looks like that PR will change how oneOf is handled by using interfaces instead of class inheritence.

Given this change only affects annotations, there will be a (small) collision on needing to rectify the annotations on the interfaces. I don't see any major issues with this change going in first given it's isolated to annotations

[MelleD]

Looks good

[cachescrubber]

You changed a sample configuration which is already removed in master, bin/configs/spring-mvc.yaml. Could you please update your branch?

[cachescrubber]

do you want me to somehow respond to this?

I just wanted to express that there iss another pending PR heavily relying on the JsonTypeInfo to work properly and I want to make sure this does not affect the implementation there.

[wing328]

I've changed the target branch of this PR to master (as it will be released as 6.0.0).

Please resolve the merge conflicts and let me know if you need help on that.

[rpost]

Please resolve the merge conflicts and let me know if you need help on that.

Rebased and squashed.

[jbeullen]

This change introduces a change in the OpenAPI specification.
The following snippet is valid:

"discriminator": {
  "propertyName": "species",
  "mapping": {
    "Dog": "#/components/schemas/Dog",
    "Cat": "#/components/schemas/Cat",
    "Tiger": "#/components/schemas/Cat"
   }
}

The OpenAPI specification allows for n species to be mapped to 1 component type.
This MR has now put the following limitation on the OpenAPI specification, forcing the relation to 1 to 1.
This will break all existing contracts that use n to 1 mapping.

This is described in following BUG.

This project contains a unit test that reproduces the issue.

Can this be reverted/fixed asap?