Improve parameter checks and error messages before running a simulation

[schmoelder]

Before running a simulation, parameters could be checked for sanity (e.g. correct sizes and plausible values).

Furthermore, after the simulation, simulation results could be checked (e.g., mass balance checks out).

Tools like this could be implemented in CADET-core or in higher level tools like CADET-Process

List of known issues:

• CSTR: length of FLOWRATE_FILTER
• Section continuity (See also: https://forum.cadet-web.de/t/error-in-dextrane-puls-simulation/903)
• Conistency between the last entries in the root.input.solver.sections.section_times and root.input.solver.user_solution_times

[jazib-hassan-juelich]

Before running a simulation, following check should be included:

• check the conistency between the last entries in the root.input.solver.sections.section_times and root.input.solver.user_solution_times. Any inconsistency between these two values can result in a failing simulation.

This should be included in the CADET core