refactor: dry up the body of the indexing

[tansanDOTeth]

Small QOL improvement

[tansanDOTeth]

@summraznboi gm

I noticed this reorg parameter isn't being used in the RuneUpdater. Do you have plans for it? If not, I can greatly simplify this function here.

Currently, it will process all the reorg hashes first in the loop here:

runestone-lib/src/indexer/index.ts

Lines 116 to 118 in ff1a10d

	for (const blockhash of reorgBlockhashesToIndex) {
	await this.asyncProcessBlockHash({ blockhash, reorg: true });
	}

However, I don't think the code needs to do this here. Instead, we can just set the block height further back for the latter loop, so it will start processing from the last known synced block height.

Ex, here

runestone-lib/src/indexer/index.ts

Lines 122 to 132 in ff1a10d

	let blockheight = Math.max(
	Network.getFirstRuneHeight(this._network),
	currentStorageBlock ? currentStorageBlock.height + 1 : 0
	);
	let blockhash = (await this._rpc.getblockhash({ height: blockheight })).result;
	while (blockhash !== null) {
	await this.asyncProcessBlockHash({ blockhash, reorg: false });
	blockheight++;
	blockhash = (await this._rpc.getblockhash({ height: blockheight })).result;
	}

What do you think?

[summraznboi]

Can you provide some unit tests to ensure no regressions are occurring with this refactor?