Avoid flushing pooled connections when matchManagedConnections returns no match

When no match is returned by the resource adapter implementation of ManagedConnectionFactory.matchManagedConnections, the IronJacamar pool implementation terminates non-matching connections.

There may be cases where resource adapters return null for cases where no connection matches but where the connections in the match set are not invalid though a different connection needs to be created based on the calling context (ConnectionRequestInfo).

A mechanism to avoid the termination of non-matching connections is needed to support such cases.