Default evolve method in timestepping does an step after end_time

Summary

While fixing #46 (closed), this logic was introduced: Default evolve method in timestepping does step after end_time.

Steps to reproduce

How can this be reproduced? If you can, point to specific files/configurations where the bug occurs

What is the current bug behaviour?

The final time is bigger than the end_time.

What is the expected correct behaviour?

Final time step matches or is less than the requested end_time. This way allows the caller to adapt the last dt forwarded to the do_step method.

Add them here, if you have any.