Fixed HStoreConf's site.anticache_eviction_distribution to use an enum option. Moved embedded enum out of AntiCacheManager and into separate AntiCacheEvictionPolicyType
Turned down some of the debug levels for the anti-caching stuff. Way too much information...
Converting more INFO messages to DEBUG in the EE
More turning down the level debug statements... Kids these days...
Removed the confusing and unimplemented 'site.anticache_threshold_ratio' HStoreConf parameter
Make sure that we don't mark deleted tuples from the regular table as evicted. This causes all sorts of problems... #164
There are a couple of things going on in here related to #164

First, the EE no longer tries to set a dummy partitionId in the EvictedTupleAccessException. I actually think that this is unnecessary because there is another problem with serializing the exception.
I think that we are trying to do something in the EE in a non-thread safe manner. I'm not sure what, but I think we are blowing away the EE's shared result buffer, which causes the deserialization of the EvictedTupleAccessException to get messed up.
I also commented out AntiCacheEvictionManager::readBlocks(). This method does not appear to be called by anything. It is probably safe to remove entirely.

This also has the new check to make sure that we don't try to access an evicted tuple that is marked as deleted.
Only debug output tweaks...
Commented out a method in the ExecutionEngine Java API that's not used anymore...
Restored storing the partitionId in the EvictedTupleAccessException serialization code. This is needed to make sure that we can ship the partitionId over the wire for dtxns