Phoenix 180

First revision for review.  There are some open points here.  Still no test case added to consume the stats.  Will do the performance test once the system is available with me.

     this will be a bit easier if the guideposts are sorted already
Ideally the guideposts should be sorted because we are inserting the guideposts with the following rowkey - tablename, fam and regioname - so considering there is only one fam those sets of guideposts would be sorted i feel. 
Another is, if the scan has to retrieve the row that is part of the guidepost itself then the splits that we form from the guideposts, will actually needs to be incremented by +1 (last byte) so that the upperrange of the key range could be used as the stop row and will cover the exact row that is as part of the guide posts.