## What kind of change does this PR introduce?
* Replaces #854 
* Fixes #853, #904 
* We don't need to remove the existing session prematurely. This causes
some issues when users want to implement some sort of switch-account
functionality since the existing session will always be removed
regardless of whether the signup / sign-in attempt succeeds.
* It's safe to remove `_removeSession` since calling `_saveSession`
multiple times will just replace the existing session

## What kind of change does this PR introduce?

This adds the SIGNED_OUT event missing in some logic that clears/logs
out the session.

## What is the current behavior?

#853

🤖 I have created a release *beep* *boop*
---


##
[2.65.1](supabase/auth-js@v2.65.0...v2.65.1)
(2024-10-14)


### Bug Fixes

* Call `SIGNED_OUT` event where session is removed
([#854](supabase/auth-js#854))
([421d7d4](supabase/auth-js@421d7d4))
* improve `mfa.enroll` return types
([#956](supabase/auth-js#956))
([aca7870](supabase/auth-js@aca7870))
* move MFA sub types to internal file
([#964](supabase/auth-js#964))
([70cecdb](supabase/auth-js@70cecdb))
* remove phone mfa deletion, match on error codes
([#963](supabase/auth-js#963))
([3547cd9](supabase/auth-js@3547cd9))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>