Capture a JS/C++ stack trace when logging ReplayErrors #417
Description
Right now it doesn't log anything except the IDL API that failed, if there was any. In the future, replay errors can be logged in place of the EventLoopInputExtent assertion.
In many cases just a stack trace is enough to figure out where the nondeterminism came from. So, it would be nice for the ReplayError constructor (or something leading up to it) to capture a stack trace.