Previously the proxies that make up the DebugEvaluate implementation for
Wasm frames lived in wasm-js.cc, but that was quite confusing since

(a) the rest of the debug support for Wasm lives in wasm-debug.cc (and
    we intend to eventually unify the DebugEvaluate and Scope objects),
    and
(b) the wasm-js.cc file is explicitly about the WebAssembly JS API
    that's part of the WebAssembly specification, and the DebugEvaluate
    proxies aren't part of that.

Bug: chromium:1162229, chromium:1071432, chromium:1127914
Change-Id: I63016dcace6d8e2af4a03c8eed4f02d464c1dee1
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2609418
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Commit-Queue: Zhi An Ng <zhin@chromium.org>
Auto-Submit: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Zhi An Ng <zhin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#71911}