smallrye-open-api Upgrade to Jandex 3.0.0

I noticed someone created the 2.3.x branch, but it was branched off of the 2.2.0 tag, which I believe is not right. So this PR, targeting the 2.3.x branch:

fast-forwards the 2.3.x branch one commit after the 2.2.0 tag in the 2.2.x branch ([maven-release-plugin] prepare for next development iteration);
fixes the <tag> element in the POM, as that should read HEAD outside of release commits;
changes the <version> elements to say 2.3.0-SNAPSHOT;
upgrades to Jandex 3.0.0.

With this PR merged to current 2.3.x (which points to a6d1ad538e), I believe the 2.3.x branch would be in the correct state. Next, we would close #1227 (as we want to keep 2.2.x on Jandex 2.x). We could also close #1228, if 3.0.x is really automatically created from 2.2.x -- I believe we would actually also move 3.0.x to be based on 2.3.x.

Makes sense, or do I completely misunderstand how SmallRye OpenAPI is managed? Thank you!

Aug 30 '22 10:08 Ladicek

Also, if you wanna take the first 3 commits from this PR and push them to 2.3.x directly, that would be fine with me :-) Or any other way you wish, of course.

Aug 30 '22 10:08 Ladicek

@Ladicek , this is good, thank you. Please go ahead and close the 3.0.x and 2.2.x PRs and I'll update the main PR and this with the changes for type references. A 3.0-RC is manually generated each time a release of 2.x occurs, with only the Jakarta changes applied with the to-jakarta.sh script. Once 3.0 is released that will stop, of course.