feat: tracing added for imply and open telemetry

[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 primarily focuses on updating the documentation and code to improve consistency in parameter naming, specifically changing instances of client to client_. It also introduces new tracing functionalities and updates client handling in various methods.

Detailed summary

• Changed parameter name client to client_ in multiple .mdx files and TypeScript files.
• Added new tracing functionalities in TraceHeader class and related methods.
• Updated documentation for TraceHeader methods.
• Enhanced header tracking in client methods.
• Improved error handling and client tracking in various smart account actions.

The following files were skipped due to too many changes: yarn.lock

✨ 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	Apr 1, 2025 9:13pm
aa-sdk-ui-demo	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 1, 2025 9:13pm

[graphite-app]

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.

[moldy530]

this looks great, there might be one case to check here though. So we initially added the headers on all clients. However, we ended up having to do it just on alchemy clients because adding headers was causing issues for someone who was using aa-sdk core to call a different RPC provider. that RPC provider was throwing errors due to unknown headers or extra headers being added