Different error handling

[andreasaporito]

The error handling right now has a certain ratio but could be modified.
For example now in case of 0 division the program does not stop but just output the fact that the method will diverge

[andreasaporito]

An initial draft idea was done in commit 32353be for example.
We would just need to throw the exception in compute_step and then catch it in Solver::solve if we wanted to use such exceptions

[andreasaporito]

Instead, to end the program in such case, we would just need to do how it is done in ReaderBase::make_config_from_map, line 151, where we stop the execution in case the input is invalid for a Bisection method interval, with std::exit(EXIT_FAILURE);