Support configuration of schemas for complex types

[MikeEdgar]

Fixes #1600

Support more complex types (besides simply a fully-qualified class name required by the MP TCK) when using the mp.openapi.schema. configuration prefix.

For example, to support a field of type JsonNullable<String> mentioned in the issue, the following could be configured:

mp.openapi.schema.org.openapitools.jackson.nullable.JsonNullable<java.lang.String>={ \
  "name": "JsonNullableString", \
  "type": "string", \
  "nullable": true, \
  "description": "A string that may be nullable!" \
}

This configuration would result in all usages of JsonNullable<String> being set to a $ref of #/components/schemas/JsonNullableString.

[MikeEdgar]

PR needs some cleanup and a few more tests, but generally done.

@melloware, please comment if you do not think this would cover your use case.

[melloware]

Gotcha so for Booleans I could do...

mp.openapi.schema.org.openapitools.jackson.nullable.JsonNullable<java.lang.Boolean>={ \
  "name": "JsonNullableBoolean", \
  "type": "boolean", \
  "nullable": true, \
  "description": "A boolean that may be nullable!" \
}

[MikeEdgar]

That's right. New-lines are only to make it easier to read and aren't required, just FYI

[melloware]

This is good with me!

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2 Code Smells

91.8% Coverage
0.0% Duplication