osdc: Constrain max number of in-flight read requests

The ObjectCacher now keeps track of the number of in-flight
read-request bytes.  If the number of in-flight read-request
bytes surpasses the cache size, the read request will be
delayed until previous read requests finish.  This prevents
the cache usage from ballooning in size during read-heavy ops
such as copy-up from a cloned image parent.

Fixes: 9854
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
Agreed.  I was also thinking about overriding the cache size so that the test case could drastically reduce it from the default 128M.