gh-156780: Emscripten: add missing EM_JS_DEPS

[clementperon]

Split out of #156781, as suggested by @hoodmane.

EM_JS bodies are emitted verbatim, so Emscripten's dependency tracker cannot see the JS symbols they reference and silently omits them.

Declared here: $FS, $PATH, $FS_getMode, $resolveGlobalSymbol and emscripten_exit_with_live_runtime in emscripten_syscalls.c, and $wasmTable, $wasmMemory, $addFunction, $addOnPreRun in emscripten_trampoline.c.

No change for MAIN_MODULE builds. Without it, the link now fails with

error: undefined symbol: $resolveGlobalSymbol

instead of a ReferenceError during initRuntime.

• Issue: Emscripten: static (non-MAIN_MODULE) builds fail at startup on dynamic-linking-only JS helpers #156780

[clementperon]

@hoodmane first PR that add the EM_JS_DEPS() everywhere

[freakboy3742]

Noting that CI is currently failing because of a duplicated symbol; that seems to suggest there's a need to collate these declarations into a single coherent location so that we can avoid duplication, rather than co-locating them with usage.

Also - can I ask that you please don't force push. We don't care about a "messy" commit history; CPython uses merge commits, so any messy history isn't preserved after merge. Force pushes also mean that we can lose the context for review comments, and it's really easy to force push a merge comment that pings the entire core team for comment.

[hoodmane]

Emscripten's normal style guide is to put these next to the symbol that uses them so I think that's alright. I think we have a conflict with #156335, need to merge a main that includes that commit and fix the duplicate symbol.