fix: correct sibling logic when reading type from schema annotation

[Mattias-Sehlstedt]

Pull Request

Thank you for contributing to swagger-core!

Please fill out the following information to help us review your PR efficiently.

---

Description

Introduces an intermediate fix for the issue reported in #5235. It does not solve the sibling handling in its entirety, since it only adjusts the type if types contains a single value (this is aimed to give a fallback for the logic implemented for OAS 3.0. This since type and types are now better isolated from each other, and the resolver expect the user to use the right field for the right OAS version).

For OAS 3.1 it is currently not possible to entirely handle types since it is converted into a single type that is fed into AnnotatedType. For a real scenario the entire type array should be utilized and passed along.

This also comes with the behavior of coercing the string value for the type into a PrimitiveType. This might in turn lead to format or similar being calculated for integer, which might not always be what one expects when using @Schema(types = {"integer"}).

Fixes: #5235

Type of Change

• 🐛 Bug fix
• ✨ New feature
• ♻️ Refactor (non-breaking change)
• 🧪 Tests
• 📝 Documentation
• 🧹 Chore (build or tooling)

Checklist

• I have added/updated tests as needed
• I have added/updated documentation where applicable
• The PR title is descriptive
• The code builds and passes tests locally
• I have linked related issues (if any)

Screenshots / Additional Context

[Mattias-Sehlstedt]

Closed since this goes further than solving the initial issue and instead also starts to try to implement proper type overriding. That is better left as separate issue since it should be a feat if it is even of interest to implement.