fix: path through history

[gilescope]

Overview

This PR attempts to provide a path through history for how historical blocks should be treated.

The data files have been compiled from the associated network's indexer db.

But after that the actual order for spent transactions was extracted from a running rpc node for the highlighted blocks (as indexer does not order the events in the same way as node does because it doesn't read the node events, it gets then from ledger).

Sunsetting

Once each environment has been chain reset, that environment's datafile can be deleted.
Once all environments have been chain reset (I'm assuming post mainnet we'll probably refresh pre-prod) then all these files and the mechanism can be deleted.

🗹 TODO before merging

• Update preview
• Works against pre-prod
• Prove syncs to tip against qanet.

📌 Submission Checklist

• Changes are backward-compatible (or flagged if breaking)
• Pull request description explains why the change is needed
• Self-reviewed the diff
• I have included a change file, or skipped for this reason:
• If the changes introduce a new feature, I have bumped the node minor version
• Update documentation (if relevant)
• Updated AGENTS.md if build commands, architecture, or workflows changed
• No new todos introduced

🧪 Testing Evidence

Please describe any additional testing aside from CI:

• Synched with preview to 75k blocks

🔱 Fork Strategy

• Node Runtime Update
• Node Client Update
• Other:
• N/A

Links

#686