Better error stack trace when aborted for waitFor and asIterator

[Luluno01]

Proposal: optimize error stack trace

Currently, the abortion error for waitFor and asIterator contains only information of the abortion point. A complete abortion error should indicate the following:

1. Where the asynchronous operation was issued (caller stack trace of waitFor and asIterator)
2. Why and where the asynchronous operation was aborted (whatever error caused the abortion and the stack trace of the abort call)

The implementation may use Error.captureStackTrace (may be polyfilled by constructing a new Error instance).

As a result, the new abortion error will have an additional cause property linked to the old abortion error.