broken job statistics are under-estimates

A number of broken job states that are the result of unexpected failures (input was apparently valid but no results were generated by the calculation after the job completed) are not actually counted as broken jobs by the server. This case was observed in one arbitrary failure for a MAFFT job(the job was fine, but the server ran it incorrectly).

****** ADDITIONAL INFORMATION ******

I've added code into the MAFFT job sevice implementation to report broken jobs in the ActivityLog so they are counted in the stats - otherwise they are simply marked as 'incomplete'.