In case a job is aborted, say because of doing a condor_rm in the
local condor queue, the job abortion should trigger a failure to be
recorded in the database.
In the case, where postscripts are associated with the jobs, the
postscript failure captures teh job failure. However, in case where
there is no postscript assocaited then the failure is not
captured. this fixes it.
the JOB_ABORTED event is now logged into the stampede database in the
jobstate table.
this is the event that gets generated when you condor_rm a job.