`SolutionStrategy.after_nonlinear_failure` saves time step data causing weird visualization

[vlipovac]

The base solution strategy at line 477 calls self.save_data_time_step() after a time step failes to converge.
If the time manager then goes back in time and reduces dt, and converges, it results in a weird visualization where the simulation jumps back and forth in time.

weird.mp4

To me this is unexpected behavior, useful only for debugging maybe.
Should this be removed? Or at least made optional?