swap order that errors are raised when auto-running fails

[EdwardLarson]

the component's error is now at the bottom of the stack trace, so the user sees it first

One sentence summary of this PR (This should go in the CHANGELOG!)
Tweak how errors are raised when auto-running components, so the actual root cause is not buried

Link to Related Issue(s)
If a component is auto-run (which is common, every analyze or unpack are auto-runs for example) and it raises an error E, then the job service also generates it's own error F with info about why the component was chosen by the auto-run. Previously the errors were raised as raise F from E, which resulted in the stack trace printing error info in the order:

E
F

So what a user sees most obviously is some junk about the auto-run, and the root cause is buried halfway up. This also translates to the GUI when there is a backend error: Since F is the most proximate error, that auto-run info error is the one shown in a pop-up when there is a backend error.

Please describe the changes in your request.
Do raise E from F instead, so errors are printed in the order:

F
E

And the most recent stuff printed is about the root cause that the user cares about. The info about why the component was selected is still there, if it will be useful for debugging.

Anyone you think should look at this, specifically?

[EdwardLarson]

As an example of the effect in the GUI, here's how an error is displayed before and after this PR:

[rbs-jacob]

I like that this is a fairly simple fix that will have a major usability impact! Both in the GUI and for API users working at the command line.