feat(transaction-controller): extend isSimulationEnabled to accept optional TransactionMeta argument

[matthewwalsh0]

Explanation

The isSimulationEnabled constructor option on TransactionController previously had the type () => boolean, giving consumers no visibility into which transaction triggered the check. This made it impossible to implement per-transaction simulation policies (e.g. skip simulation for certain transaction types, origins, or chain IDs).

This change updates the callback signature to (transactionMeta?: TransactionMeta) => boolean. The argument is optional so the change is backward-compatible — existing consumers that pass () => boolean continue to compile without modification. All three call sites that have a TransactionMeta in scope (#updateTransactionInternal, #updateSimulationData, #updateGasEstimate) now forward the meta; the two remaining call sites (estimateGas, estimateGasBuffered) and the batch utility pass no argument, which is valid given the optional typing.

The matching isSimulationEnabled member of AddTransactionBatchRequest in batch.ts is updated to the same signature.

References

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
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them