Bug 5990: SCT wasn't refreshing when paused in RPL Debugger after slot range change
Bug Number: 5990
Release notes (y/n): Yes
For Release Nums: 7.2 (or maybe 7.1.2)

Certain SCT updates are repressed during a Run.  That means that when a run 
completes (or pauses), the SCT has to perform an update for those that had 
been dropped during the Run.  The SCT was doing this correctly for Run 
Controller-based "pauses", but not for pausing (e.g. hitting a breakpoint) 
in the RPL debugger.

These two new callbacks are now generated from Rpl/RplDebugger.  Only the 
first one is used to fix this bug; the second one was added for completeness, 
as these events are paired.

   RPL_DEBUGGER_PAUSED -- generated from notifyExecutionPaused()
   RPL_DEBUGGER_RESUMED -- generated from notifyExecutionResumed().

The SctModelData class now registers for callbacks from the RplDebugger.
See processing of the RPL_DEBUGGER_PAUSED callback in method:

   SctModelData::rplDebugCallbackHandler (
      CallbackType, CallbackData*, void* clientData);

In testing, it was confirmed that those two callbacks are generated when 
hitting a RPL Breakpoint and Resuming (respectively) -- and also when 
Stepping in the RplDebugger.