WL#2411: Integrate long-run tests into Connector/J QA Release Process

Take the long-run tests from WL#2334, and come up with suitable test parameters
to check for memory leaks, and to prove a hypothesis that connection pools with
short idle times do not create issues for spikey load situations (which is
counter-best-practive in Java, but usually because connections take a long time
to setup, which is not true w/ MySQL).

Run these tests on Win2k3, Linux and Solaris, and report results, as well as run
these tests for some long period of time before release (1 week or more) to
determine stability of code to be released.