Update deployment descriptors for Concurrency 3.1

[KyleAure]

Updates our deployment descriptors for new values added for Concurrency 3.1 from the following sources:

• virtual=true annotation atrribute (hint to request virtual threads jakartaee/concurrency#349)
• qualifiers annotation attribute (concurrency resources via @Inject and with qualifiers jakartaee/concurrency#348)
• Deployment Descriptor schema (Concurrency 3.1 - Add virtual and qualifier elements to resource definitions jakartaee/jakartaee-schemas#44)

I think I'm most of the way there just have some questions tagged with //TODO that need some further review.
Would appreciate some feedback @tbitonti.

[LibbyBot]

Code analysis and actions

DO NOT DELETE THIS COMMENT.

• 21 product code files were changed.

• Please describe in a separate comment how you tested your changes.

• 1 messages files were changed and need an L2 review.

• @OpenLiberty/message-reviewer Please review.

• dev/io.openliberty.concurrent.internal/resources/io/openliberty/concurrent/internal/resources/CWWKCMessages.nlsprops

• 1 NLS files were changed and need an ID review.

• @OpenLiberty/message-reviewer Please review.

• dev/io.openliberty.concurrent.internal/resources/io/openliberty/concurrent/internal/resources/CWWKCMessages.nlsprops

[jantley-ibm]

ID review comments attached. Let me know if you have questions or concerns about suggested changes. When we have agreed on changes, I will add the "ID reviewed" label.

[tbitonti]

I reviewed the parser changes. I did not look at the runtime updates. I see a few very minor updates (missing copyright, a possible name change). The function looks good.

[KyleAure]

@njr-11 @tbitonti @jantley-ibm Updated based off your feedback.

[njr-11]

Added a comment about merging. I'm fine if you defer this to a separate pull.

[njr-11]

I don't think this will behave correctly for a more complex type like Class[].
mergeAnnotationValue in InjectionBinding does newValue.equals(oldValue) which will be an instance comparison for arrays. It looks like there is a special variant, mergeAnnotationProperties, to handle merging for the properties, and it is even more complex in that it appears to combine individual properties from one list into the other rather than just overwriting. Should the qualifiers behave similarly where the merge is a combination of the annotation values and <qualifier> elements? Or should the set of the latter replace the former?

This same comment will apply to all 4 resource types.

[KyleAure]

Haven't done any builds on this yet and still waiting on reviews. I think I'll tackle this now.

[KyleAure]

@njr-11 Resolved this by adding an extra check when we merge XML values under this commit b181523 (#27148)

[posmith]

Support message review completed.

[KyleAure]

Force pushed to resolve merge conflicts.

[njr-11]

Yes, we need to be careful with making it a requirement to load classes if we aren't certain we can have the right class loader when doing it. There might be different class loaders between modules and for the application. If we don't have access to the correct class loader here, another option would be to perform the merge as String class names, to be loaded later. I'm not sure what is available. You'll need to work with Tom on this part.