feat: Add afterAdd hook to transaction controller

[matthewwalsh0]

Explanation

Add optional afterAdd hook to mutate transactions added via addTransaction method.

Persist original transaction params in new txParamsOriginal property.

References

Fixes #4688

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed, highlighting breaking changes as necessary
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

[jpuri]

Hey @matthewwalsh0 : I have a query about these hooks approach, but this can result in code written in clients and also replicated across extension / mobile.

[matthewwalsh0]

Hey @matthewwalsh0 : I have a query about these hooks approach, but this can result in code written in clients and also replicated across extension / mobile.

From the perspective of the controllers, they're just injection points for custom logic so we can decouple from other domains and client specific decisions such as smart transactions, delegations, and snaps.

But if the same hook is needed in both clients, there is nothing stopping the hook being defined within another controller or central package, and the hook just invoking that via the messenger, as we should indeed avoid duplication where possible.