FEATURE: Better exception handling when eel fails

[mhsdesign]

Currently if you use a malformed expression, or the expression yields an error its hard to debug, in which property path the exception was caused.

ideally an exception would look like:

expression in template path: `childNodes.bar.properties.someProperty` threw Error: ...

it a bit tedious but a simple implementation could look like:

                try {
                    $propertyValue = $this->eelEvaluationService->evaluateEelExpression($propertyValue, $context);
                } catch (\Exception $exception) {
                    throw new \Exception(sprintf('Property "%s": "%s" could not be evaluated.', $propertyName, $propertyValue), 1684257493838, $exception);
                }