MB-12642:bp:MB-10437:prefer oldest waiter in concurrency_throttle
MB-12642:bp:MB-10437:prefer oldest waiter in concurrency_throttle

Old behavior could choose same pid(s) over and over again. Which
caused particular problem for initial replication under slight udpates
load. I.e. it would repeatedly pick already mostly up-to-date vbuckets
over vbuckets that still need to be replicated. Which would cause very
short batches which in turn would cause very slow rebalance.

By picking oldest waiter (modulo system clock jumps which should be
infrequent) we avoid this problem. It should also help at least
somewhat for the case of ongoing replication under somewhat heavy but
not too heavy load, due to better avoidance of too short replication
batches.

Change-Id: Ie6dcafabd510367015c1e5897a620e37eb7a17f5
Orig-Reviewed-on: http://review.couchbase.org/38368
Reviewed-on: http://review.couchbase.org/43227
Reviewed-by: Aliaksey Kandratsenka <340b8e09ca65cd3fc686427fcfed17e87eaf61e2@gmail.com>
Tested-by: Aliaksey Kandratsenka <340b8e09ca65cd3fc686427fcfed17e87eaf61e2@gmail.com>

membase/ns_server,ceejatec/ns_server,mschoch/ns_server,mschoch/ns_server,nimishzynga/ns_server,ceejatec/ns_server,nimishzynga/ns_server,membase/ns_server,mschoch/ns_server,nimishzynga/ns_server,membase/ns_server,nimishzynga/ns_server,membase/ns_server,membase/ns_server,membase/ns_server,ceejatec/ns_server,ceejatec/ns_server,ceejatec/ns_server,ceejatec/ns_server,mschoch/ns_server,mschoch/ns_server,mschoch/ns_server,nimishzynga/ns_server,nimishzynga/ns_server