Idea: Remove "stop" from subroutines

[EduardoJauch]

The idea is to change the actual behavior of the model, that causes to the model to stop inside inner functions/subroutines, where there is no contextualization of the error, making very difficult to understand the problem.

A very easy example is the "GetData" routines in the ModuleEnterData.
If an error is found while inside them, the model stops, and it is not possible to know which module input file was being read or which keyword/block.

The correct behavior is to the routines to return with the "stat" variable with the error, and so on, up to a higher level, where the context can be show to the user, making easier to it to understand the problem.