fix(native): resolve symbol names in crash stacktraces on macOS

[tustanivsky]

This PR fixes address-only crash callstacks produced by the native backend on macOS - frames carried bare instruction_addrs with no function names, so the Sentry's external crash reporter (and any consumer of the client-side event) displayed unreadable stacks.

Problem

The crash daemon has no symbol resolution on macOS. enrich_frame_with_symbol is compiled for Linux/Android only (ELF, #1836) and the Windows path resolves names through dbghelp (#1811). On macOS the daemon's frame-pointer walk only attached the containing module to each frame and never set function.

Proposed fix

Implement the macOS counterpart of the ELF resolver in the daemon:

• Resolve names from the Mach-O symbol table (LC_SYMTAB/nlist_64) of the containing module, read from disk out-of-process. Universal (fat) binaries are resolved to the slice matching the daemon's architecture. Tables are scanned in fixed-size chunks with only the winning name read from the string table, and the resolved source is cached per module - large tables are never loaded wholesale.
• Bound matches with LC_FUNCTION_STARTS: nlist entries carry no size (unlike ELF st_size), so a name is only accepted when a symbol sits exactly at the entry of the function containing the address. The payload survives strip, so addresses in symbol-table gaps stay unresolved instead of being attributed to unrelated neighboring functions - an unresolved frame beats a wrong name.
• Validate files by LC_UUID equality with the loaded image (the Mach-O analog of the GNU build-id check). This also correctly rejects on-disk stubs of system dylibs that don't match the dyld-shared-cache images actually loaded; those frames are left for server-side symbolication.
• Follow the dSYM companion (<X>.dSYM/Contents/Resources/DWARF/<binary>) when the module's own table misses (stripped local symbols), checked both next to the binary and next to the enclosing .app bundle (the UE packaged-game layout), UUID-validated.

Testing

Checked manually against a UE 5.8 sample project (packaged Development build, macOS) by capturing a null-pointer crash:

• Invalid crash callstack example
• Correct crash callstack example (mangled function names)

Related items

• fix(native): resolve correct symbol names for crashes in multi-module apps on Windows #1811
• fix(native): resolve symbols from split-debug files on Linux #1836

[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 443094a. Configure here.}

[jpnurmi]

Now that all integration-tested desktop platforms are covered, we could drop the "win32 or linux" conditions in test_integration_native.py:

sentry-native/tests/test_integration_native.py

Lines 997 to 1001 in 252e4c6

	if sys.platform == "win32" or sys.platform == "linux":
	# At least some frames should have symbolicated function names
	assert any(
	frame.get("function") is not None for frame in exc["stacktrace"]["frames"]
	)

sentry-native/tests/test_integration_native.py

Lines 1044 to 1048 in 252e4c6

	if sys.platform == "win32" or sys.platform == "linux":
	# At least some frames should have symbolicated function names
	assert any(
	frame.get("function") is not None for frame in exc["stacktrace"]["frames"]
	)