Call reconnects after leaving

[VisasIespejas]

Which package/packages do you use?

• @stream-io/video-react-sdk
• @stream-io/video-react-native-sdk
• @stream-io/video-client

Describe the bug
Call will sometimes reconnect after leaving. For me this happens in React development mode when double render causes useEffect to join and leave a call in quick succession (see snippet below for useEffect logic).

To Reproduce

1. Use this code snippet in React development mode:

let promises = Promise.resolve();
function serially(promise) {
  promises = promises.finally(() => promise());
}

export default function App() {
  const [state, setState] = useState<any>(null);
  useEffect(() => {
    const callCounter = ++counter;
    const client = StreamVideoClient.getOrCreateInstance({
      apiKey,
      user,
      token,
    });
    const call = client.call("default", callId);
    call.state.callingState$.subscribe((state) =>
      console.log(`[${callCounter}] call state ${state}`),
    );
    let isActive = true;
    serially(() =>
      call.join().then(() => isActive && setState({ client, call })),
    );
    return () => {
      isActive = false;
      setState(null);
      serially(() => call.leave());
    };
  }, []);
  return (
    state && (
      <StreamVideo client={state.client}>
        <StreamTheme>
          <StreamCall call={state.call}>
            <SpeakerLayout />
            <CallControls />
          </StreamCall>
        </StreamTheme>
      </StreamVideo>
    )
  );
}

2. Open the example in browser and allow permissions (you may need to reload multiple times for this to happen)
3. You may see that the user has joined the call twice. The console logs will show something like this:
   
   Here you can see that call [1] has reconnected after leaving.

Expected behavior
Leaving the call happens cleanly and it does not reconnect.

Screenshots
Here you can see that the user has connected twice, because call reconnected after leaving:

Version

• SDK version 1.8.1

React / JS client

• Browser: Edge 131.0.2903.86
  (I experienced the issue in all browsers, but seems to happen more consistently in edge for me)

Node JS client

• Node version: v20.16.0

Additional context
Add any other context about the problem here.