Fixes parent hash processor and ethereum updater ext to handle block hash correctly

[cabrador]

Description

This PR fixes issue with hoodi dataset.
It contains:

1. fixes to ethereum updater extension - correctly ending and beggining new txs.
2. fixes to parent hash processor extension which includes saving block hashes instead of state root hashes. Note: Special aida-db with block-hashes is necessary for that. To create this aida-db this tool is necessary for recording the block hashes and then using util-db merge to merge it to an existing aida-db with hoodi substate.

I was able to process hoodi dataset aida-vm-sdb with lfvm and carmen go-file and validate-tx flag up to block 200500.

Fixes #174

Type of change

• Bug fix (non-breaking change which fixes an issue)

[codecov]

Codecov Report

Attention: Patch coverage is 86.36364% with 6 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
utildb/info.go	0.00%	2 Missing ⚠️
cmd/util-db/db/info.go	0.00%	1 Missing ⚠️
...ecutor/extension/validator/state_hash_validator.go	50.00%	1 Missing ⚠️
utildb/clone.go	0.00%	1 Missing ⚠️
utildb/validator.go	0.00%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[matejmode]

• could you work this into Add State Hash substate#39 will be fixed in following PRs
• as statehash is the only table with differently stored block key - instead of prefix+bigEndian it uses prefix+hexEncoding, could you also unify this to store both block hash and statehash with bigencianencoding?
• clone custom is also missing - will be fixed in following PRs