Debugger tab breakpoint gutter markers are missing and stale during paused runs

The debugger tab opened when execution paused at a breakpoint, but its read-only code editor did not show breakpoint gutter markers. Users could see and interact with breakpoints in the normal source editor before running, but once the app stopped in the debugger tab the same breakpoints were invisible there. Clicking the gutter in the debugger tab also did not reliably update the running debug session, so a breakpoint removed while paused could still be hit again after continuing.

Expected behaviour: the debugger tab should show the same breakpoint markers as the normal editor, allow them to be toggled or edited while paused, and immediately apply those changes to the active debug session. If the paused line has a breakpoint, the breakpoint marker should take precedence over the current-line gutter indicator so the two markers do not overlap.

Impact: breakpoint state was confusing during stepping and could appear stale while debugging desktop or remote runs.