Fix autotracker period throttle, Dirty flag, and Lua debugger exception pause

[emosaru]

Summary

• MemorySegment.ShouldUpdate: fixed an inverted CompareTo sign (> 0 → < 0) that caused memory segments to update on every 30 ms poll tick until the period elapsed, then never update again — the exact opposite of the intended throttle behavior. MemoryTimer had the correct sign the whole time.
• LuaMemorySegment: the Lua callback's return value is now captured; a truthy result clears Dirty so normal period-based throttling resumes after each successful update. Previously Dirty was never cleared.
• LuaDebuggee.EnterExceptionPause: added an early-out guard (HasActiveSession) so Lua errors at runtime don't enter the DAP exception-pause path — including its log line — when no debugger is attached.
• MemorySegment: made abstract (was already effectively abstract via the OnSegmentDataUpdated virtual no-op).

Test plan

• Connect an autotracker and verify memory segment callbacks fire at their configured period (not every 30 ms)
• Confirm a segment with a returning-true callback stops showing as dirty after the first successful update
• Trigger a Lua error with no DAP debugger attached — confirm no EnterExceptionPause log line appears
• Trigger a Lua error with a DAP debugger attached and exception-break enabled — confirm pause still works

🤖 Generated with Claude Code