JITL Job checkHistory does not set error attribute when checking job chains

Current Situation

When checking a job chain or an order in a job chain with the checkHistory JITL job, all checks for errors will not work as the error flag is not set correctly for orders. E.g. the query=lastcompletedrunEndedSuccessful always returns true even if the last completed run was not successful.

Desired Behavior

When checking a job chain or an order in a job chain with the checkHistory JITL job, all checks for errors should work. E.g. the query=lastcompletedrunEndedSuccessful should return the correct value depending on the value for RESULT_ERROR in the table REPORTING_TRIGGERS