Fixed bugs in RunJobs

[jhnaldo]

The expected result of the following result is printing "reachable" and throwing 42:

async function f() {
  await 0;
  print("reachable");
}
f();
throw 42;

However, the current ESMeta only throws 42. It happens because the RunJobs algorithm directly returns the result when the result of a job is an abrupt completion, no matter whether the job queue is empty or not.

This PR fixed this issue, and now ESMeta prints the "reachable" string and throws 42.