fix: sending multiple uos with deferred action

[howydev]

We currently don't handle two cases well:

Problem 1. Reusing the client to send a 2nd UO, after consuming the deferred action. This is because we set the deferredActionNonce and deferredActionData to be used, but we don't update this after the UO is sent, so the 2nd uo includes the DA which causes a validation revert
Solution: Initialize these values with some defined "falsy" values and update the values to these falsy values after using the DA.

Problem 2. Initializing a new client to send a 2nd UO also doesn't work. If we don't use a nonce override, the entity id and global validation options ends up being the default value (the owner). Also, we always have a defined deferredActionData value whether the DA has been consumed or not, so it always gets prepended to any sig even if the DA is consumed, also causing a validation revert
Solution: Parse entity id and isGlobalVal options, and the falsy value for deferredActionData from above is set to undefined so it wouldn't be used if the DA has been consumed

This PR adds two tests to test the above - sending a 2nd UO from the same client as well from a new client instance.

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 handling of deferred actions in the smart contract system, ensuring proper management of signatures and nonce values, and refining the logic for processing user operations.

Detailed summary

• Changed const sig to let sig in signUserOperationHash for nativeSMASigner and singleSignerMessageSigner.
• Updated signature concatenation logic to clear deferredActionData after use.
• Added entityId and isGlobalValidation fields in parseDeferredAction.
• Modified deferredActionData type to include specific formatting.
• Improved nonce handling logic in createMAv2Base.
• Updated tests to cover new deferred action flows and ensure correct client behavior.

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

[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.

[github-actions]

🌿 Documentation Preview

Name	Status	Preview	Updated (UTC)
Alchemy Docs	✅ Ready	🔗 Visit Preview	Apr 11, 2025, 7:56 PM