Bug Fix

added new cases to yaml test
new implementation of isOneSided=isRelevant
and isEvaluateOperator
they now evaluate both sides of edge at once instead of one at a time
fix and that should be or

fix, now  a few plan changes that look possibly better
working correctly and new tests

changes made to isRelevant to fix previous buts
tests added to dphyp test for edge cases
cleanup and notes

cleanup and notes
switch to immutable rows
undo change that didn't fix anything
added function in Row to check bindings sensitivity + implemented a conservative method (i.e., return true always) in subclasses
added check before making an immutable row
added test
tweaks
projectRow isBindingsSensitive()
Merge remote-tracking branch 'fdb/master' into pipelining
map-join-project-outer.expected error fix

cleaned up expected that had improper output, also small cleaning for
clairity
All yaml tests are passing at this point; still need to narrow down the row classes that aren't bindings sensitive
changed isBindingsSensitive in Expression and AbstractValuesHolder rows, still passing everything
HKeyRow -> not sensitive to bindings
InternalValuesRow -> not sensitive to bindings
NullsRow, PersistitGroupRow -> not sensitive to bindings
RowDataRow, TestRow -> not sensitive to bindings
all row classes should have appropriate isBindingsSensitive