op-reth - Blocked waiting for execution cache mutex/OOM if pruning enabled

**Bug Description**

https://github.com/paradigmxyz/reth/issues/19682 - original issue with all the necessary info, TLDR: if op-reth has pruning enabled - it will report Blocked waiting for execution cache mutex and after some time it will be killed OOM even with 128GB RAM, the problem started with op-reth v1.9.2

**Steps to Reproduce**

resync/download snapshot with pruning enabled

**Expected behavior**

**Environment Information:**

last tested on Ubuntu 24.04, op-node v1.16.1

**Configurations:**

these were the params for pruning:
--prune.senderrecovery.distance 2592000 \
--prune.accounthistory.distance 2592000 \
--prune.storagehistory.distance 2592000 \
**Logs:**

**Additional context**

---

⚠️ **Notice:** Issues that do not include the following sections will be subject to closure:
- Bug Description
- Steps to Reproduce
- Environment Information

Please ensure all required sections are filled out accurately to expedite the debugging process and improve issue resolution efficiency.

Start with the linked reth issue, then reproduce a resync or snapshot download with pruning enabled using the listed --prune.*. Confirm the execution-cache mutex blocking and eventual OOM under the stated environment; done means the pruning-enabled workflow completes without those symptoms.

Written by the indexing model from the issue text.