feat: add alchemy transport update for the mav2 account client

[Blu-J]

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 focuses on enhancing the SMAV2AccountClient functionality by integrating Alchemy support, improving type definitions, and modifying the client creation process to accommodate different transport types.

Detailed summary

• Added imports for Alchemy-related types and functions in client.ts.
• Enhanced SMAV2AccountClient type definitions to support Alchemy transport.
• Introduced CreateSMAV2AlchemyAccountClientParams type for Alchemy-specific parameters.
• Modified createSMAV2AccountClient to handle both standard and Alchemy transports.
• Updated the implementation of createSMAV2AccountClient to return either SmartAccountClient or AlchemySmartAccountClient.

✨ 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	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 11, 2025 1:22am
aa-sdk-ui-demo	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 11, 2025 1:22am

[Blu-J]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• feat: add alchemy transport update for the mav2 account client #1271 👈 (View in Graphite)
• feat(client): multi account light and alchemy consolidation #1264
• test(test-d): add test-d files for vitest typechecking: #1248
• feat(aa-sdk): sdk light client can call the alchemy client #1236
• main

---

How to use the Graphite Merge Queue

Add the label graphite-merge-queue to this PR to add it to the merge queue.

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

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[moldy530]

couple nits and just some questions for my own understanding but overall LGTM

We should probs also test the types at a minimum that with AlchemyTransport we get an Alchemy client and any other transport we get a non Alchemy Client

[moldy530]

nit: we should be able to just pull this up and remove line 115 below since the account instance can be created the same way regardless of the client

[moldy530]

for my own understanding: does it complain if this is just SmartAccountClient? technically the AlchemySmartAccountClient is a SmartAccountClient