Do not guard calls mesa_error() with report_ierr

[pmocz]

The user flag report_ierr = .true. is used as a debugging tool to report diagnostics on internal errors in Mesa but not stop the code. Flipping the switch to true should not change the outcome of the simulation. Therefore, we should not call mesa_error() inside if(report_ierr == .true.) if statements. Either always just halt the code, or use guards like if(stop_for_bad_nums == .true.).

There are just a handful of cases in the code where this pattern was not followed. This is dangerous because it can cause non-reproducible results when someone is trying to debug their run switches report_ierr = .true. on. Particularly in simulations that chain more than one inlist. For example, running ./run_all for the 20M_pre_ms_to_core_collapse test problem with report_ierr = .true. was yielding a different result than switching diagnostics off because one of the inlists in the middle of the chain was ending prematurely and the next inlist restarted the simulation from the last photo written.

TL;DR: fix so that switching on diagnostics reporting does not change outcome of the simulation