Merge Read and Write Quota

Combined GET and GETALL to GET
Combined PUT and DELETE to PUT
It would be cleaner if we rename the new GET to READ and PUT to WRITE
But it might break the backward compatibility so leaving it like this
for now.
Made the read quota take all GET_ALL keys into account
Releasing Voldemort 1.8.15
bdb native backup fixups

1. add message for native backup status
2. add bdb env config param: bdb.recovery.force.checkpoint
QuotaException causes delete failure

1) When QuotaException is thrown by delete, it fails the delete instead
of Quorum to decide the failure.
2) Added unit test to cover some part of the delete test case.
Releasing Voldemort 1.8.16

Releasing voldemort 1.8.16
ZoneShrinkage endToendTest fails

Zone is shrinked when the nodes receive get/put traffic.
The bootstrap URL is set to node 1 and node 0 is removed at the end
of zone shrinkage. Zone shrinkage metadata is written to nodes in order.
So first node 0 receives the update, that it is no longer part of the
cluster. But before node 1 is updated, the bootstrap code retries to
bootstrap from node 1. This is a race condition between admin client
setting correct metadata on all nodes and the client threads refreshing
the old value from other nodes. The problem is update metadataversion
properties fail as the node 0 is not longer a part of the cluster.

The race condition will be avoided if the bootstrap url and the node
in which we first write the metadata change are one and the same.
This is what this specific fix does, by making sure node 0 is not removed
during zone shrinkage.
Recursively translate file permissions