Extract interpreter call-paths from FunctionValue / GeneratorValue

[frostney]

Summary

Extract the interpreter call-path methods from FunctionValue / GeneratorValue so those shared units stop depending on the evaluator.

Why

Goccia.Values.FunctionValue.pas and Goccia.Values.GeneratorValue.pas uses Goccia.Evaluator and call EvaluateExpression on their interpreter call paths, while the VM uses its own TGocciaBytecodeFunctionValue.Call. Those references keep the evaluator linked into every binary.

Current behavior

The shared value units embed interpreter-only Call / ExecuteFunctionBody paths that call into the evaluator.

Expected behavior

• The interpreter call paths are removed or relocated so FunctionValue / GeneratorValue no longer use the evaluator.

Scope notes

• A coupling to sever before deletion (Delete the tree-walk interpreter (~16k LOC) and collapse the CI mode matrix #875). Parent Remove the tree-walk interpreter #825.