Bug: Exit action triggered twice when invoked machine escalates from final state

[andrejpavlovic]

Description

If a child machine has a top-level exit action, this action will be triggered twice when the child machine ends in a final state that triggers an escalate action.

Basically a child machine like this one will trigger exit action twice when reaching final cancelled state.

const childMachine = createMachine({
  predictableActionArguments: true,
  id: "child",
  initial: "start",
  entry: () => {
    console.log('child-entry')
  },
  exit: () => { // <-- triggered twice when reaching final `cancelled` state
    console.log('child-exit')
  },
  states: {
    start: {
      on: {
        COMPLETE: "completed",
        CANCEL: "cancelled"
      }
    },
    completed: {
      type: "final"
    },
    cancelled: { // <-- final cancelled state
      type: "final",
      entry: actions.escalate({ type: "cancelled" })
    }
  }
});

send('CANCEL')

Expected result

child-entry
child-exit

Actual result

child-entry
child-exit
child-exit

Reproduction

https://codesandbox.io/s/ecstatic-euler-pqtsfj?file=/src/index.js

Additional context

• Tested with version 4.38.2
• Used to work fine with version 4.32.1, regression starts with 4.33.0 and higher
• Regression most likely caused by Add xstate.stop event and fix exit handlers execution #3126
• Looks like latest v5 (5.0.0-beta.20) also has this issue. Repro https://codesandbox.io/s/silly-maxwell-49h4v5?file=/src/index.js