Make `run_locally(ensure_success=True)` raise the actual encountered exception

[janosh]

when debugging a failing workflow with run_locally, it can be very helpful to have access to the exception object. currently, you always get the same generic error:

jobflow/src/jobflow/managers/local.py

Line 181 in e61b50f

raise RuntimeError("Flow did not finish running successfully")

to see what went wrong, you have to run with

run_locally(log=True, ensure_success=True)

and then hunt for the error message in the logs which can be verbose

how about we raise the actual error message instead of this generic RuntimeError? a (possibly bad style) sketch of how to implement this:

for the above to work, _run_job would have to be modified to return the caught exception:

[janosh]

pinging @utf @Andrew-S-Rosen @JaGeo in case you have thoughts?

[jmmshn]

Second this.

Also,
The raise_immediately flag kind of handles this:

jobflow/src/jobflow/managers/local.py

Line 24 in e61b50f

raise_immediately: bool = False,

I feel real-world exceptions are so deep down the call stack that reading things becomes problematic.
I have been running this flag and

ipython --pdb test.py

to debug workflows and it's been pretty effective.

[janosh]

thanks for the tip! i'll give the raise_immediately=True + ipython --pdb combo a try