docs: send user operations eoa doc

[RobChangCA]

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?

https://app.asana.com/0/1208241431426251/1208700857883332

---

PR-Codex overview

This PR introduces a new section on handling Externally Owned Account (EOA) connections in the send-user-operations.mdx file, detailing how to use the SDK for user operations without explicitly specifying a Smart Contract Account (SCA) client.

Detailed summary

• Added a section titled Handling EOA Connections.
• Explained that EOA connections do not require an SCA client.
• Described how the SDK automatically detects EOA connections.
• Provided a code example using useSendUserOperation to send a user operation.

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
aa-sdk-site	❌ Failed (Inspect)			Jan 16, 2025 6:48pm
aa-sdk-ui-demo	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 16, 2025 6:48pm

[graphite-app]

Your org has enabled the Graphite merge queue for merging into main

Add the label “graphite-merge-queue” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge.

You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link.