check metadata incorrect results, hard analysis

Fix the new admin metadata check command and did the same change
for old admin command.

1) If check metadata fails it says true or false but not the
  actual failure.
2) Check metadata sometimes incorrectly reports failure depending
   on the order in which stores are returned.
3) Check metadata will reprot success if a store is completely missing
   from one of the nodes. It does not track number of times retrieved.

With this commit the check metadata is done using a map.

For stores check
The map will be from storeName to (map from store defintion
to nodeName)

for other
The map will be from object of that key to nodename.

This map will be used for consistency check. This map will group non
matching information to groups for easier analysis. The lenght of the
value in the map will be evaluated for missing information, solving the
problem 2 and 3 listed above
Merge pull request #178 from arunthirupathi/checkMetadata

check metadata incorrect results, hard analysis
Using standard logger in the StreamingClient constructor
Merge pull request #182 from FelixGV/log_StreamingClient_construction_properly

Use standard logger in the StreamingClient constructor
Add overwrite option to fork lift tool

If the key already exists in the destination cluster, forklift tool
will not overwrite the key. With the intent of supporting read only
cluster data to be fork lifted to the read/write cluster, overwrite
option is being added. If the newly forklifted data does not contain
the entire key set from the old, then the new data will be the mix
of old and new. The old data should expire sooner than the new one
enforced by the retention policy.
Incorporate code review comments

Fix error message
Change the order of if/else
Merge pull request #183 from arunthirupathi/forkLiftOverwrite

Add overwrite option to fork lift tool
bdb native backup fixups