Investigate Geth and Erigon snap sync failures when syncing from scratch

[Filter94]

Impact

environment [Testnet]

an user is impacted [Y], if yes type of user: [Internal]

Describe the bug

I noticed that when upgrading Geth after 1.15.8 snap sync doesn't sync Geth nodes from scratch. For Erigon the issue seems to be similar post version 3.0.2. Right now we're using full sync in the e2e tests, but we need to investigate what's the issue with the snap sync and raise it with the client teams if necessary or come up with a workaround

Steps to Reproduce

In the E2E test

Steps to reproduce the bug:

1. Set Geth version to 1.16.3
2. Set the sync mode to SNAP
3. Try to run the test
4. See a failure of the sync from scratch scenario, saying that Geth is at height 0
5. See error in the logs "Parent is not found"

Actual result

The test is failing, there is an error in Geth logs

Expected result

Geth should sync without any issues

[Filter94]

I tested on Devnet, Geth 1.16.3 node is starting up in Snap sync mode there without issues and it's syncing in 30 minutes

My hypothesis is that Geth can snap sync client only from another Geth Snap sync server. This means that in an E2E test we need to actually upgrade the Geth 1.13 to 1.16, because that seems to be the only way to get the initial Geth Snap Service post the switch

[Filter94]

I think for Geth I'll leave it in Full sync mode, because changing it to SNAP is too complicated and it doesn't provide much value for Maru testing