Replace timing measurements in idle_pool_max_conns

The test uses hard-coded time limits to evaluate whether queries are being served on time. This has shown to not be a reliable way of measuring how well the feature is working and it keeps failing. Something other than the time it takes to run all queries need to be used as the metric, potentially per query latencies to see how fair the scheduling is.