The EE's TableIterator now supports nested iterators. This will allow us to combine iteration of a PersistantTable + EvictedTable in a single iterator
Removed more unncessary debug statements. Never use System.out. People are abusing my baby...
Minor tweaks to the logic for the nested TableIterator. It turns out that this is actually not what we want to do for SeqScanExecutor...
When we throw an EvictedTupleAccessException down in the EE we no longer need to provide the partitionId. It is not set automatically in the PartitionExecutor
Lots of good stuff here. I'm committing this while sitting at the gate in Chicago waiting to take off...

I reorganized SeqScanExecutor so that it will always scan the EvictedTable after the regular scan. We have to create two different iterators because the schemas of the two tables will be different.

I also think I fixed the random crashing problem in the EE when we throw the EvictedTupleAccessException. I switched our internal access tracker to use an std::vector instead of std::list

Expanded tests to make sure that we check all the different access paths with evicted tuples. I will continue to expand this on the flight right now.
Expanded test cases in TestAntiCacheManagerTPCC
Fix for the failing test. It's commented out for now but it might be enough to get going...