Correct the false 'bytecode VM has no evaluator dependency' doc claim

[frostney]

Summary

Correct the docs that claim the bytecode VM has no evaluator dependency.

Why

docs/bytecode-vm.md and docs/architecture.md state the bytecode executor has no dependency on the interpreter/evaluator. That is false today — TGocciaVM.ExecuteDirectEval calls EvaluateEvalProgram (Goccia.VM.pas:12117), so the VM uses Goccia.Evaluator.

Current behavior

The docs assert an independence that does not hold until the eval-port (#872) lands.

Expected behavior

• The docs are corrected to describe the real eval coupling, then updated again once Port eval() / direct-eval to compile-to-bytecode (sever VM -> evaluator dependency) #872/Delete the tree-walk interpreter (~16k LOC) and collapse the CI mode matrix #875 remove it.

Scope notes

• Documentation; pairs with the eval-port (Port eval() / direct-eval to compile-to-bytecode (sever VM -> evaluator dependency) #872). Parent Remove the tree-walk interpreter #825.