Missing binary name in issue stacktrace when identified with debug_id

### Environment

SaaS (https://sentry.io/)

### Steps to Reproduce

Upload an event that has a stacktrace frame with `debug_meta` containing `debug_id` but not `code_file`. `code_file` is optional according to https://develop.sentry.dev/sdk/data-model/event-payloads/debugmeta/#mach-o-images

If dsyms are included for this debug_id the frame will symbolicate and you will get a symbol name + file.

### Expected Result

The stack frame UI should show the name of the binary that was symbolicated

### Actual Result

The UI will not show the binary name, and just show ``

### Product Area

Issues - Source Maps

### Link

https://portola.sentry.io/issues/7266158906/events/7c5bfc390c214ff69379fd43788092a1/?environment=App%20Store&project=4506735735865344&query=is%3Aunresolved%20mechanism%3Amx_hang_diagnostic&referrer=next-event

### DSN

_No response_

### Version

_No response_

Start with the event payload's debug_meta fields, especially debug_id and the optional code_file, then trace how a symbolicated stacktrace frame supplies its binary name to the stack frame UI. Reproduce the case with a debug_id but no code_file, including dsyms, and consider the work done when the symbolicated binary name is displayed instead of .

Written by the indexing model from the issue text.