Preventing "Run to" debugger command from raising update events, in order to prevent unnecessary (and broken) updates

[adri09070]

Fixes #607

In the debugger, "run to" from the debugger action model is doing steps on the debug session, which raise an update for each step.

However, to update the variable list in the inspector, the debugger uses the previousASTScope from the debugger action model, which isn't updated after each step when performing "run to". This could lead to duplicated temp variables when using "run to" to execute an inlined loop (see #607).

One simple solution is to prevent the debugger from updating after each step performed by the command, making only one big update after all steps instead.

This is cohesive with what the command should do because if we perform "run to" instead of steps, this is because we don't care of the intermediary updates.
This also makes the "run to" command A LOT faster.

The fix is for P12 but another similar fix should be done for P11 to fix #607 on P11