Discussion: racing for replies

### Is your feature request related to a problem?

Actually if a node do a quorum_read to get some data, it will ask 3 near nodes and will wait for the 3 replies to continue the work.
If one of these "near nodes" is really slow, this quorum will wait until timeout.

Could we ask for more nodes and then only take the fastest 3 for example?

### Describe the solution you'd like

We could change the `consistency_level` flag to be a pair `{nbRespToContinue, nbMsgToSend}`

### Additional context

What do you think?

Start by locating the quorum_read implementation and the consistency_level handling for requests to near nodes. Review how replies and timeouts currently control continuation, then determine the intended behavior for sending more requests and continuing after the fastest required replies; done means the design is agreed and the behavior is covered by tests.

Written by the indexing model from the issue text.