Final state of an execution is not correctly displayed

In order to be able to step back in the history the recording of the execution stops before the last step even if it as been executed.
This leads to incorrect/misleading information in the UI.

For example when using the K3FSM official example, an do a Run/Resume up to the end
we obtain:

We can see that the execution correctly reached the end because the console shows that the whole string has been consumed. However, the variable view still show the penultimate state (same for the stack)
The timeline looks correct but is stuck to the penultimate step (7). (the hovering shows the correct information when hovering on step 8 in the timeline)

It would be clearer for the user to introduce a virtual "End" step (similar to the virtual "Initialize Model" step) that would simply copy the content f the last step but will help to indictate that even if the engine is not stopped, the execution reached it end (according to its semantic)

Ideally these virtual steps would have a special representation in the timeline in order to clearly identify them.

This virtual step would also help in the modeling workbench test in order to know if the simulation has reached the end by looking in the engine execution context.