feat: add useSendUserOperation and useDropAndReplaceUserOperation hooks

[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 new hooks useSendUserOperation and useDropAndReplaceUserOperation for interacting with Alchemy smart accounts in React components.

Detailed summary

• Updated error message in NoAlchemyAccountContextError class
• Added useSendUserOperation and useDropAndReplaceUserOperation hooks
• Created corresponding components for each hook
• Updated sidebar links
• Updated exports in alchemy/src/react/index.ts
• Added meta information for new hooks in documentation pages

The following files were skipped due to too many changes: packages/alchemy/src/react/hooks/useSendUserOperation.ts

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

[denniswon]

ditto comment made in another hook pr:

or 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

[moldy530]

See my comment in the use client actions hook about this. I don't think this is a generic error. There's nothing to check in the account context that will make it more informative. The client here is a parameter to the hook and can be null. If it's null we error. Beyond that what else can we pull from context? What if the user is passing in a client they didn't create via context and it's still null?

[denniswon]

you are right. I left a similar comment on signer hook prs, and left similar comments here, but I realized that the core SDK takes care of these already.

[denniswon]

this is only meant to be used for smart accounts? we should check if account is connected to the client, not just that client exists. in general, throw more informative state error back to the caller.

Makes sense to group signer/smart account/modular account hooks separately in the subdirs of hooks for different accounts, and also have more common state checking/error messages/code shared.

[moldy530]

The client will throw if it is not connected to an account already and the typing on this specific client parameter forbids it from not not being connected anyways since it has to be a LA client or MA client

The base branch was changed.