Provide information why job submission failed

[askask]

If job submission with jobManager.runJob(job) fails, it would be useful if there was more information why it failed.
Maybe add an additional field to BEJobResult.

[askask]

Actually it would be good to get the error message from the underlying job scheduler in every case where BE fails to execute a command.

[vinjana]

Maybe put the message into the BEJobResult? Consistency with other sites may suggest to use an Exception that encodes the details (code + message).

[vinjana]

TODO:

• get exit code
• parse error message from stderr/stdout of submission command
• consistent would be to put this into an exception (JobSubmissionException?)

[vinjana]

Execution error (exit code != 0)
-> Exception out of ExecutionService (including STDOUT & STDERR of command).
-> Issue #93.

Parser error (exit code == 0)
->

Timeout error (no exit code)
->

Investigate further the 3+ cases and make individual issues.

[vinjana]

Consider RoddyToolLib issue TheRoddyWMS/RoddyToolLib#32 about logging output of failed locally executed processes. Maybe provide this information to the result object in BE?