Properly handle newly created "correlated" indicator in marshalled plan for expression scan

MB-29710 adds support for expression term and subquery term as right-hand side of ANSI JOIN. As part of the change a new "correlated" indicator is added to plan.ExpressionScan. If we have a mixed mode cluster of Vulcan and Mad-Hatter, a plan generated on the Vulcan node will not have the correlated indicator, and if that plan is then executed on the Mad-Hatter node, we may incorrectly use the newly introduced runtime cache for the expression evaluation, which may generate incorrect result if the expression is actually correlated.

This is kind of a part of a large issue where the marshalled plan currently does not have any versioning information, which makes handling of such things (newly introduced fields) more difficult.