prop.get and Session::expression_errors (Reveal Expression Errors, the
viewer's error banner) built their expression context without the
footage source, so an expression that reads footage pixels
(sampleImage) gave a different value or a spurious error there while
it worked in the render and in expr.errors (#1000).
expr_tools::eval_ctx builds the render's context (expression host and
footage source) for a comp at a time; expr.errors, prop.get,
Session::expression_errors and the script value query all use it.
Fixes#3231
Property.expressionError only compiled the expression, so one that compiles
but throws or yields a non-finite number read as "" while expr.errors
reported it. It now evaluates the property's expression at the comp's
current time through the same per-property check expr.errors uses
(expr_tools::property_error), without rendering anything. Without an
evaluator, an enabled expression falls back to the syntax check.
Fixes#3219
Add the helper to the expression editor's completions (syntax highlighting and auto-complete) and to the Expression Language menu's Interpolation group, so accepting it inserts the call parentheses like linear/ease.