Database connection pooling as Mirth Connect resource

[dfauraz]

Using the database connectors, mirth connect creates and drops a new DB connection for every message processed.
With a lot of messages, this makes millions of DB connections opened and closed every day, which is a waste of
resources (file descriptors, network, CPU ...) and sometimes leads to errors (Too many open files ...).

A better approach would be to use DB connection pools.
This should not be very difficult because mirth already has hikari for its own DB connections.
Working with javascript is always possible, but we do not use mirth to write code ...

This has already been requested in:
#2171
I try again here : please vote for this very sensible feature :)