Expand context available for expression evaluation

[hntd187]

For #270 I came to realize a lot of the context we need to do some more elaborate or intelligent expression parsing would require us to expand the context available to expression evaluation.

What @scovich mentioned here #270 (comment) we have a lot of matching of various pairs of expressions, but converting scalars to more literal numeric values has several problems with conversion without knowing types up front. I think the current kind of expression evaluation is inefficient but works in it's current state, I think there is discussion to be had regarding how we might augment this to work with EngineData and rework ArrayData to more efficiently handle some of these cases where blowing out an expression to be copied to ever row is not ideal.