History-attached stack traces

[StoneCypher]

Saw a good comment criticizing XState on Reddit. Reached out to its author u/tossed_ to ask about opinions.

They dropped several good new features.

One is the idea that, as it's hard to debug the actions that a machine takes on its own once the call stack from the thing which invoked said behavior is discarded, it might be a good idea to attach the call stack itself to the history trace inside the machine.

That's gonna get slow fast, so, hide this behind a constructor flag, please