Allow Java EE components other than MDBs to consume messages asynchronously

Nobody has claimed this yet.

This proposal suggests the addition of the following annotation: @MessageSelector, to be used on a @MessageDriven bean consumimng a Queue or as Topic Subscriber.

Example:

```
package sample;

// imports

@MessageDriven(mappedName = "jms/queue0")
public class MessageSelectorBean implements MessageListener {

@Resource(lookup = "jms/connectionFactory")
ConnectionFactory connectionFactory;

@MessageSelector("(StockSector = 'Technology')")
public void onMessage(Message message) {
try (JMSContext context = connectionFactory.createContext()) {
String request = ((TextMessage)message).getText();
Destination replyDestination = message.getJMSReplyTo();
TextMessage replyMessage = context.createTextMessage("Reply to: "+request);
context.createProducer().send(replyDestination, replyMessage);
} catch (JMSException ex) {
// log an error here
}
}
}
```
#### Affected Versions
[2.0]

The issue names no files, tests, or entry points. Start by reviewing the Jakarta Messaging specification and clarifying whether @MessageSelector applies beyond MDBs; done requires an agreed API design for asynchronous message consumption and its scope.

Written by the indexing model from the issue text.