e3: investigate why Prune added before commit caused exec fail

[AskAlexSharov]

Steps to reproduce:

go run ./cmd/erigon snapshots rm-all-state-snapshots --datadir=/mnt/erigon/
go run ./cmd/integration stage_exec --datadir=/mnt/erigon/ --chain=sepolia --reset
go run ./cmd/integration stage_exec --datadir=/mnt/erigon/ --chain=sepolia --batchSize=16m

[WARN] [06-13|03:12:16.126] [7/15 Execution] Execution failed        block=1450743 txNum=3659752 hash=0x2b907fdf319049dd137d98f51f7329f7f23519895ca33e5f2c560b4a6225c430 err="invalid block, txnIdx=94, gas used by execution: 2025274, in header: 2030476, headerNum=1450743, 2b907fdf319049dd137d98f51f7329f7f23519895ca33e5f2c560b4a6225c430"

By git bisect i currently found that regression was introduced between:

Previous HEAD position was ccde7c0938 buildVI: nil decompressor passed fix (#10558)
HEAD is now at db2e5d3973 e3: keep less blocks in db (#10521)

[AskAlexSharov]

git bisect shows that regression introduced by https://github.com/ledgerwatch/erigon/pull/10561 revert (by https://github.com/ledgerwatch/erigon/pull/10730 ) helps - but maybe it's just hiding some bug in prune

[AskAlexSharov]

maybe fixed by https://github.com/erigontech/erigon/pull/11803

[AskAlexSharov]

not fixed by https://github.com/erigontech/erigon/pull/15166