Prepare to release 1.7.0
Roll forward to release 1.7.1 (same as 1.7.0)
Co-ordinator GetAll fails for some data

1) Unit tests for GetAll had a bug, which did not fail the tests.
   The values were compared, but the tests did not fail when the
   values does not match. created a method assertValueEquals to
   handle this scenario.
2) The client deserialization used the getContent method which
   corrupted the binary data. Now using getRawInputStream. But not
   sure about the difference between the getInputStream and
   getRawInputStream.
3) Wrote 2 new tests to check all possible byte data for co-ordinators
  ( get, getall )
4) Refactored some of the unit tests to use a common code path.
Fixing default value for quota limiting config in VoldemortConfig
Compute Quota Usage per operations per store

-- Usage pct computed per call and averaged over a 1 minute window
-- Unit tests included to compare measured usage pct against actual throughput
Prepare to release 1.7.2
Wrapping RESTClient in LazyStoreClient

   1) Separated inner config class from RESTClientFactory to
RESTClientFactoryConfig
   2) RESTClientFactory.getSToreClient(storeName)  now returns a
LazyStoreClient
   3) Removed the instantInit boolean in LazyStoreClientConstructor.
Instead introducing a boolean for use by RESTClientFactory

Removing LazyStoreClientTest.java
Releaseing Voldemort 1.7.3