Implement ERC-7821 calldata compression in ERC7579Utils

[Amxx]

ERC-7821 implementation uses the ERC7579Utils library. While ERC-7821 looks like a subset of ERC-7579, it includes a specific design choice to help compress calldata that is not strictly part of ERC-7579.

When asked if it would be fine to add this mechanism to ERC-7579, Konrad (ERC-7579 authors) says:

Hadrien Croubois, [21/03/2025 09:56]
[...]. Since we are using the same library for 7821 and 7579 implementations, I was wondering if it would be ok to add the same behavior to 7579.

Konrad | rhinestone, [21/03/2025 22:51]
I dont see a problem with this but one point to note is that this will cause differing behaviour to existing accounts, so you can't really rely on that feature working across accounts

This PR adds the target rewrite mechanism to be used in both 7821 (where it is required) and 7579 (where is is not mandated, but also not a problem).

---

No need for a changeset entry if this is part of 5.3 audit fixes (unreleased feature).

PR Checklist

• Tests
• Changeset entry (run npx changeset add)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5558c87

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ernestognw]

I understand the CI is failing because we would need to implement changes from #5600 into the release-v5.3 branch

Can we point to master instead and then cherry pick into release-v5.3? We should do this together during tomorrow's sync

The base branch was changed.

[Amxx]

updated to target master