Change some tests' outputs re: evaluating erased function parameter for function expressions

Consider the following
```
def x =
    println("impure")
    0

def f(erased a: Int) = 0

// first try
f(x)
// second try
{ println("block"); f }(x)
```

Previously, we do not print `impure` in the first try,
but we do on the second try.
This is an inconsistency that the current compiler fixed.

Both now do not evaluate `x`.

Author: natsukagami

tests/run-custom-args/erased/erased-27.check

@@ -1,3 +1,2 @@
 block
-x
 foo

tests/run-custom-args/erased/erased-28.check

@@ -1,4 +1,2 @@
-x
 foo
-x
 bar