fix(native): resolve correct symbol names for crashes in multi-module apps on Windows

[tustanivsky]

Summary

This PR fixes incorrect/irrelevant function names in crash callstacks captured by the Native backend on Windows for applications composed of many modules.

Problem

When the daemon walks the crashed process's stack (walk_stack_with_dbghelp) it resolves frame addresses to function names via dbghelp initialized with a NULL symbol search path. With no search path dbghelp can't locate each module's PDB and falls back to the module's export table mislabeling internal (non-exported) functions with the nearest exported symbol.

This stays invisible for monolithic apps but breaks for multi-module apps where the relevant code is split across many DLLs scattered across different directories. dbghelp misses most of those PDBs so the frames that matter come back with unrelated names and a callstack looks irrelevant to the actual crash even though the frame addresses are correct.

A concrete example is the Unreal Engine Editor where code is split across many UnrealEditor-*.dll and plugin modules living in many separate Binaries/ directories so crashes there produced mislabeled stacks while packaged (monolithic) game builds did not.

Proposed fix

Build a symbol search path from the directory of every loaded module (already available in crash_ctx->modules[]) and pass it to dbghelp via SymInitializeW so it can find each module's PDB next to its DLL (the equivalent of cdb -y <dirs>).

• Thread crash_ctx into walk_stack_with_dbghelp
• Build a deduplicated ;-separated directory list (case-insensitive dedup; cached, since the walker runs once per thread)
• Add SYMOPT_FAIL_CRITICAL_ERRORS | SYMOPT_NO_PROMPTS to keep the unattended daemon from blocking on dbghelp dialogs; keep SYMOPT_DEFERRED_LOADS so symbol loading stays cheap with many modules.

Windows-only; other Native-backend platforms resolve symbols through different paths and are unaffected.

Related items

• fix(win): resolve correct symbol names in client-side stack traces for multi-module apps crashpad#156
• Incorrect Callstack Show for Crashpad crashes whenCRASHPAD_ENABLE_STACKTRACE is Enabled sentry-unreal#1422

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 95d13d0. Configure here.}