Fix the test in InvalidMissingAncestorReOrgSyncTest, ref https://hive.ethpandaops.io/#/test/generic/1772181860-0161f15e42e305dde23a1cb982021954?testnumber=323

FAIL (Invalid Missing Ancestor Syncing ReOrg, Timestamp, EmptyTxs=False, CanonicalReOrg=False, Invalid P8):
TEST ISSUE - Failed to set invalid block: failed to commit state: commit aborted due to database error:
    missing trie node bcce1472eb9dba20d7c6261be584a4f269252a86becefd17c0179c4a9daebdc2 
        (owner 37d65eaa92c6bc4c13a5ec45527f0c18ea8932588728769ec7aecfe6d9f32e42)
        (path ) 
    unexpected node: (37d65eaa92c6bc4c13a5ec45527f0c18ea8932588728769ec7aecfe6d9f32e42 []),
        ...

The engine simulator uses SetBlock to force-insert sidechain blocks, including invalid ones.
SetBlock used the payload parent StateRoot as the only source of truth for state reconstruction.

After inserting invalid blocks, that root can be non-replayable in the local path-scheme trie, so the next insertion fails with:

failed to commit state ... missing trie node.

So proposed to change:

• Track the actual committed state root produced by SetBlock for each inserted block hash.
• When inserting a child block, try the provided parentRoot first.
• If it fails, retry from the tracked committed root of the parent hash.
• Store the newly committed root for subsequent insertions.

This keeps sidechain injection progressing even when payload-header roots on invalid branches are not replayable.

also closes #1382