OP: investigate fast sync related segfault in e2e tests

[bap2pecs]

I was trying to optimize our tests run time and added

cfg.FastSyncInterval = 4 * time.Second
cfg.FastSyncLimit = 100

to overwrite the default values but got:

https://app.circleci.com/pipelines/github/babylonchain/finality-provider/2033/workflows/819dcba3-8977-4759-a4f2-b3f6c2e55a35/jobs/6007/parallel-runs/1?filterBy=ALL

I think this might imply some serious problem which I think it's worth looking into

based on the error logs:

[signal SIGSEGV: segmentation violation code=0x1 addr=0x7f82a5e7fab2 pc=0xed752a]

goroutine 304421 [running]:
runtime.throw({0x6e73c94?, 0xc00586e900?})
	/usr/local/go/src/runtime/panic.go:1077 +0x5c fp=0xc005d42f48 sp=0xc005d42f18 pc=0x4409bc
runtime.sigpanic()
	/usr/local/go/src/runtime/signal_unix.go:875 +0x285 fp=0xc005d42fa8 sp=0xc005d42f48 pc=0x459f85
github.com/cometbft/cometbft/proto/tendermint/crypto.(*Proof).Unmarshal

seems exact root cause as #508 which we never really understood the root cause

also seems that simply changing the parameters triggered the problem again

cc @lesterli @SebastianElvis