exekall: Fix use of UnEvaluatedExprVal

Build them with the right Expression, instead of the Expression of their
consumer. That was incorrect and lead to strange behavior where the
value to be computed was replaced by an UnEvaluatedExprVal that was
originally created for one of its parent, masking the error.