Add retry policy manager for failed transactions

[GabrielMartinezRodriguez]

Linked Issues

• closes https://linear.app/happychain/issue/HAPPY-110/txmanager-allow-retry-policy-customization

Description

Introduces a new RetryPolicyManager to handle transaction retry logic in a more modular way. The manager determines if failed transactions should be retried based on their receipt and revert reason. Currently implements retry logic for "Out of Gas" errors, either by checking gas consumption or explicit revert messages.

Key changes:

• New RetryPolicyManager with extensible interface for custom retry policies
• Integration with TransactionManager for configurable retry behavior
• Refactored transaction monitoring to use the new retry policy system

Toggle Checklist

Checklist

Basics

• B1. I have applied the proper label & proper branch name (e.g. norswap/build-system-caching).
• B2. This PR is not so big that it should be split & addresses only one concern.
• B3. The PR targets the lowest branch it can (ideally master).

Correctness

• C1. Builds and passes tests.

• C2. The code is properly parameterized & compatible with different environments.

• C3. I have manually tested my changes & connected features.

• C4. I have performed a thorough self-review of my code after submitting the PR.

Architecture & Documentation

• D1. I made it easy to reason locally about the code.
• D2. All public-facing APIs & meaningful internal APIs are properly documented.
• D3. If appropriate, the general architecture of the code is documented.

[cloudflare-workers-and-pages]

Deploying happychain with    Cloudflare Pages

Latest commit:	95598fd
Status:	✅  Deploy successful!
Preview URL:	https://7fc8403d.happychain.pages.dev
Branch Preview URL:	https://gabriel-retry-policy.happychain.pages.dev

View logs

[GabrielMartinezRodriguez]

• Add retry policy manager for failed transactions #299 👈 (View in Graphite)
• Txm no longer receives Viem objects #298 : 1 other dependent PR (#300 )
• Add flush mechanism #289 : 1 other dependent PR (#297 )
• Allow run multiple txm simultaneously within the same service #285
• Added docs for txm #272
• Mutex in tx monitor #264
• Purge transactions #232
• Txm hooks #229
• Use kysely instead of mikro-orm #250
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[linear]

HAPPY-110 txmanager: Allow retry policy customization

We should allow users to implement their own retry logic with code or perhaps through a configuration when a transaction reverts

[not-reed]

this seems like it should match the return result from the viem getTransactionReceipt type. we probably don't want to/need to redefine it here do we?

[norswap]

I agree, this only add the extra typing for the status, but if we really want that (honestly, it doesn't buy us much), we can have it by extending the getTransactionReceipt return type like

export type RevertedTransactionReceipt<Status extends "success" | "reverted> =
     TransactionReceipt<bigint, number, Status, "eip1559">

[norswap]

Mostly just docs + some type changes, but otherwise this is good!

[norswap]

I agree, this only add the extra typing for the status, but if we really want that (honestly, it doesn't buy us much), we can have it by extending the getTransactionReceipt return type like

export type RevertedTransactionReceipt<Status extends "success" | "reverted> =
     TransactionReceipt<bigint, number, Status, "eip1559">

[GabrielMartinezRodriguez]

@norswap I think there was an error with the diff files in this PR because I didn't restack it, and it was showing the diff from another PR. But anyway, I think the comments you made, even if they aren't for this PR, are good and can be applied to this one.

[norswap]

Add docstring that says this retries if running out of gas.

[norswap]

Correct. What we could do here is invert the two lines, which saves on filtering the notPersistedTransactions since they'll always be included. Bit of a micro-optimization.

this.notFinalizedTransactions = this.notFinalizedTransactions.filter((transaction) =>
     NotFinalizedStatuses.includes(transaction.status),
)
this.notFinalizedTransactions.push(...notPersistedTransactions)

(current code has the reversed ordering)