chore(trie): Cleanup unused trie changesets code (#21323)

docs/crates/db.md

@@ -58,8 +58,6 @@ There are many tables within the node, all used to store different types of data
 - HashedStorages
 - AccountsTrie
 - StoragesTrie
-- AccountsTrieChangeSets
-- StoragesTrieChangeSets
 - TransactionSenders
 - StageCheckpoints
 - StageCheckpointProgresses

docs/crates/stages.md

@@ -12,7 +12,6 @@ The `stages` lib plays a central role in syncing the node, maintaining state, up
 - AccountHashingStage
 - StorageHashingStage
 - MerkleStage (execute)
-- MerkleChangeSets
 - TransactionLookupStage
 - IndexStorageHistoryStage
 - IndexAccountHistoryStage
@@ -114,12 +113,6 @@ The `StorageHashingStage` is responsible for computing hashes of contract storag
 
 <br>
 
-## MerkleChangeSets
-
-The `MerkleChangeSets` stage consolidates and finalizes Merkle-related change sets after the `MerkleStage` execution mode has run, ensuring consistent trie updates and checkpoints.
-
-<br>
-
 ## TransactionLookupStage
 
 The `TransactionLookupStage` builds and maintains transaction lookup indices. These indices enable efficient querying of transactions by hash or block position. This stage is crucial for RPC functionality, allowing users to quickly retrieve transaction information without scanning the entire blockchain.

docs/vocs/docs/pages/run/configuration.mdx

@@ -434,11 +434,6 @@ storage_history = { distance = 100_000 } # Prune all historical storage states b
 
 # Bodies History pruning configuration
 bodies_history = { distance = 100_000 } # Prune all historical block bodies before the block `head-100000`
-
-# Merkle Changesets pruning configuration
-# Controls pruning of AccountsTrieChangeSets and StoragesTrieChangeSets.
-# Default: { distance = 128 } - keeps the last 128 blocks of merkle changesets
-merkle_changesets = { distance = 128 }
 ```
 
 We can also prune receipts more granular, using the logs filtering: