Debugger tab fails to show source for qualified nested module pause locations

When debugging code from a class nested inside a module or namespace, the debugger can pause and show variables/call stack but leave the Debugger tab's code editor blank. The debugger should resolve qualified source keys such as ImpulseEngine.World back to the matching Studio source item and show the paused method body.