Flush connection's prepared statement cache on endRequest notification

As discussed in EAPSUP-671 some driver implementation may decide to close the underlying connections on endRequest notification leading to problems described in WFLY-15493. Altough, our suggestion was to don't use IronJacamar's prepared statement cache with such drivers, we may also clear the cache on endRequest notification to make sure that even in such configuration failure won't occurr.