Add 'org.gradlex:jakarta-jws-api' capability for 'jakarta.jws:jakarta.jws-api:3+' and 'jakarta.xml.ws:jakarta.xml.ws-api:4+' artifacts

[ko-at-work]

With the release of Jakarta XML Web Services 4.0 (part of Jakarta EE 10), the Jakarta Web Services Metadata Specification was folded into this respective specification.

folds Jakarta Web Services Metadata Specification into this/Jakarta Web Services Specification (Jakarta Web Services Metadata Specification is no longer available as a standalone API/project/jar)

What does this mean?

• 'jakarta.xml.ws:jakarta.xml.ws-api:4+' now includes jakarta.jws.* packages that were previously expected to be included as part of 'jakarta.jws:jakarta.jws-api:3+'

A new 'org.gradlex:jakarta-jws-api' capability should be created to that includes 'jakarta.jws:jakarta.jws-api:3+' and 'jakarta.xml.ws:jakarta.xml.ws-api:4+' so a capability conflict is detected properly.

[jjohannes]

Thank you for explaining this @ko-at-work. I also discovered that this rule is needed through a new generic test we added that compares Jar files. But I would most likely would have missed that this is only necessary starting with jakarta.xml.ws:jakarta.xml.ws-api:4+.

Resolved through #205 and #221.

Rule class with the specific version handling: JakartaJwsApiRule