CallExpression uses incorrect scope for parameters evaluation

[sys27]

Describe the bug
CallExpression has access to nested captured scope when evaluating lambda parameters.

To Reproduce
Steps to reproduce the behavior:

1. f := (x) => (y) => x + y
2. add1 := f(1)
3. add1(x + 2)

Expected behavior
add1(x + 2) returns an error because the x variable is not defined in the "global" scope.

Actual behavior
add1(x + 2) returns 4 because the call expression uses the captured scope where the x variable is a lambda parameter equal to 1. So, x = 1 and y = x + 2 = 3 -> x + y = 4