Fix state machine destructor access violation

[seer-by-sentry]

Fixes CLIENT-37R. The issue was that: StateMachine destructor accesses invalid m_currentState pointer, likely due to premature State object deletion or inconsistent state management during object destruction.

• Removed the call to m_currentState->onExit(EXIT_RESET) in the StateMachine destructor.
• This prevents potential access violations during object destruction, as the current state might already be invalid or point to deleted memory.
• The halt() method already clears m_currentState before the state machine is deleted, making the onExit call redundant and dangerous.

This fix was generated by Seer in Sentry, triggered automatically. 👁️ Run ID: 9465015

Not quite right? Click here to continue debugging with Seer.