[Bug]: Stale Hash potential issues

[aramikm]

Summary

It appears that the stale hash extension might be causing some issues with graph updates

Context

One of our providers has an issue with the graph updates. The exact reason is not currently known but it is highly likely the result of the new stale hash check extension added to ensure non valid graph transactions are going to get ignored early in the pool.

Acceptence Criterea

• Revert the changes related to stale hash check

Relevant log output

[Nest] 35  - 10/11/2024, 7:31:18 PM   DEBUG [NonceService] nextNonce 2990897
2024-10-11 19:31:19        RPC-CORE: submitAndWatchExtrinsic(extrinsic: Extrinsic): ExtrinsicStatus:: 1014: Priority is too low: (757 vs 757): The transaction has too low priority to replace another transaction already in the pool.
[Nest] 35  - 10/11/2024, 7:31:19 PM   ERROR [ReconnectionGraphService] Error processing batch: RpcError: 1014: Priority is too low: (757 vs 757): The transaction has too low priority to replace another transaction already in the pool.
2024-10-11 19:31:19        RPC-CORE: submitAndWatchExtrinsic(extrinsic: Extrinsic): ExtrinsicStatus:: 1014: Priority is too low: (757 vs 757): The transaction has too low priority to replace another transaction already in the pool.
[Nest] 35  - 10/11/2024, 7:31:19 PM   ERROR [ReconnectionGraphService] Error updating graph for user 147584, provider 2: RpcError: 1014: Priority is too low: (757 vs 757): The transaction has too low priority to replace another transaction already in the pool.
    at checkError (/app/node_modules/@polkadot/rpc-provider/cjs/coder/index.js:23:15)