Track call frames using VM debug metadata

The debugger currently relies on runtime events to detect function entry and exit. This is fragile because events may be missing or delayed, and they add unnecessary work to normal execution.

We should extend Miden VM package debug information with compact source call-frame ranges. The debugger can inspect the current execution context and reconstruct the active physical call stack directly from those ranges. Expired ranges naturally remove frames, while newly active ranges add them.

This should work for nested calls, recursion, linked packages, and instruction padding without adding overhead to the Processor’s normal execution path. Inline frames remain separate and continue using inline-call metadata.

The result should be consistent backtraces in both the REPL/TUI and DAP without requiring compiler-emitted frame start/end events.

The issue describes extending the Miden VM package debug information. Start by examining the existing debug metadata structures in the codebase, likely in the `miden-debug` crate. Look for how runtime events are currently handled and where call frames are tracked. The goal is to add source call-frame ranges to the metadata and modify the debugger to reconstruct the stack from these ranges. Testing will involve nested calls, recursion, and linked packages to ensure backtraces are consistent in the REPL/TUI and DAP without frame events.

Vom Indexierungsmodell aus dem Issue-Text verfasst.