fix: update reorg logic

[PJColombo]

It modifies the reorg handling logic by calling Blobscan API’s reorg handling endpoint before resyncing forwarded blocks.

In the event of a reorg, forwarded blocks may include transactions from rewinded blocks. If we sync the transactions from forwarded blocks first, their block field may be updated. Consequently, if these transactions were originally in a rewinded block, their reference to the old block would be lost. As a result, when calling the reorg endpoint, transactions from the rewinded block won’t be flagged as part of the reorg.