fix(txm): not process the same block multiple times

[GabrielMartinezRodriguez]

Description

While monitoring the service, I noticed that when we experience network issues, the viem onError callback is triggered multiple times per block, not just once per network error. This was causing the resetBlockSubscription function to be called multiple times, leading to race conditions such as processing the same block more than once

I removed the onError callback to address this since it's unreliable. Additionally, I implemented a mechanism to ensure that already processed blocks are never processed again.

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

Reminder: PR review guidelines

Correctness

• C1. Builds and passes tests.
• C2. The code is properly parameterized & compatible with different environments (e.g. local,
  testnet, mainnet, standalone wallet, ...).
• C3. I have manually tested my changes & connected features.

< INDICATE BROWSER, DEMO APP & OTHER ENV DETAILS USED FOR TESTING HERE >

< INDICATE TESTED SCENARIOS (USER INTERFACE INTERACTION, CODE FLOWS) HERE >

• C4. I have performed a thorough self-review of my code after submitting the PR,
  and have updated the code & comments accordingly.

Architecture & Documentation

• D1. I made it easy to reason locally about the code, by (1) using proper abstraction boundaries,
  (2) commenting these boundaries correctly, (3) adding inline comments for context when needed.
• D2. All public-facing APIs & meaningful (non-local) internal APIs are properly documented in code
  comments.
• D3. If appropriate, the general architecture of the code is documented in a code comment or
  in a Markdown document.
• D4. An appropriate Changeset has been generated (and committed) for changes that touch npm published packages (currently packages/core and packages/react), see here for more info.

[cloudflare-workers-and-pages]

Deploying happychain with    Cloudflare Pages

Latest commit:	f46fab6
Status:	⚡️  Build in progress...

View logs

[GabrielMartinezRodriguez]

• Randomness monitor service #584
• Txm traces #521
• fix(txm): returned nonce queue order #578
• fix(txm): not process the same block multiple times #577 👈 (View in Graphite)
• Fix: Viem sends random undefined blocks #575
• fix(txm): heap out of memory #573
• Avoid initiating new attempts if the gas conditions persist unchanged #571
• Dynamic priority fee #570
• TXM: Rpc liveness #562
• fix(txm): nonce gap #561
• PoC: Add metrics to TXM #503
• master

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