Query timeout UI work

The member names here are a bit of a mess.
They echo the xml source tag like "snapshot or elastic" -- that's good.
They echo the xml attribute name like "priority" -- that's good or like "throughput" -- also good, except we decided to capitalize this one -- and "maxtablesize" we decided to split up and arrange surrounding the temptable tag name instead of all at the end for "temptablemaxsize" or "temptableMaxSize". 
elasticPauseTime capitalizes words in the end part, but since it is based on the attribute named "duration", it's just wacky anyway.

"querytimeout" goes its own way -- it uses just the tag and ignores the attribute name "maxlatency". That's not very extensible for two reasons. One is that the querytimeout name is too specific -- it's easy to imagine future settings that effect snapshot or elastic, but what else is querytimeout ever going to have or be but a latency number?
If we anticipate a little that we might want to allow other kinds of controls and limits on query as a category, maybe the tag name should just be "query" and the current attribute should be maxlatency for a member name of queryMaxlatency or queryMaxLatency or timeoutlatency for a member name of querytimeoutlatency or queryTimeoutLatency.
Then we could maybe later add a warninglatency attribute to the query tag that triggers a log message -- maybe so the operator could see it and decide to cancel a long-running write.
Maybe we could also have warningoperations and maxoperations, warningtempmemory and maxtempmemory (eventually replace the badly named maxtemptablesize -- it really does apply to each query, not to the overall system).