feat: add useLogout hook

[avasisht23]

Pull Request Checklist

• Did you add new tests and confirm existing tests pass? (yarn test)
• Did you update relevant docs? (docs are found in the site folder, and guidelines for updating/adding docs can be found in the contribution guide)
• Do your commits follow the Conventional Commits standard?
• Does your PR title also follow the Conventional Commits standard?
• If you have a breaking change, is it correctly reflected in your commit message? (e.g. feat!: breaking change)
• Did you run lint (yarn lint:check) and fix any issues? (yarn lint:write)
• Did you follow the contribution guidelines?

---

PR-Codex overview

This PR adds a new useLogout hook to facilitate user logout functionality in the Alchemy package.

Detailed summary

• Added useLogout hook in alchemy package for user logout
• Updated useAddPasskey to include mutation handling
• Created ComponentWithLogout in site/snippets/react/useLogout.tsx
• Updated metadata and content in site/react/useLogout.md

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[moldy530]

Same comment here about adding a doc to this PR.

Let's get in the habit of adding docs with code changes

The base branch was changed.

[denniswon]

In general, all the hooks contain repetitive code, basically doing the same things. Any idea on better refactoring / reduced code repeats?

Also, per my inline comment, we should check from AlchemyAccountContext which state the user/account is in, and throw informative error messages instead of just throwing null exceptions or other generic error messages

[denniswon]

for all out hooks, we should check from AlchemyAccountContext which state the user/account is in, and throw informative error messages instead of just throwing null exceptions or other generic error messages

[avasisht23]

the useSigner hook will throw an error if there is no clientStore we can get the signer from (and thus the user, account, etc.).

let's chat more with Moldy when he's back. he actually advised here that i move this approach.

[avasisht23]

In general, all the hooks contain repetitive code, basically doing the same things. Any idea on better refactoring / reduced code repeats?

re: this, lemme refactor after getting this hooks stack. agree there's probably some factory method i can create and pass a mutation function unique to the hook for.

[denniswon]

@avasisht23 if we are fast-following reviewed comments/TODOs, would be great to attach asana links to the tasks for each items to be followed. Otherwise those items would be hard to track.