Devnet9 Hive Fail - peering fail on ForkID tests

[jflo]

To reproduce, i use the following setup to debug hive tests:

i hacked a thing: ethereum/hive@master...jflo:hive:local_debug_hacks

which uses this snooper as a fake client

ethpandaops/json_rpc_snoop@master...jflo:json_rpc_snoop:dualSnoopers

which you'll have to build and tag, so the hive test will use it.

then ran hive like:

./hive -sim ethereum/engine -client-file ./configs/local-client.yaml --sim.limit "engine-cancun/ForkID: Genesis at " --docker.output to isolate a single test, and step through in my debugger.

ForkID: Genesis at * are the tests failing. Suspect peers may be disagreeing over forkId.

[Gabriel-Trintinalia]

This seems to work in their environment. Need to understand what is different

[non-fungible-nelson]

Need to confirm this is still passing in the hive environment.

[macfarla]

It is failing in the hive environment. error indicates unable to connect to mock client

FAIL: Error waiting for response: could not rlp decode message: EOF

[Gabriel-Trintinalia]

Removing the code below from the fork_id.go in the engine simulator makes the tests pass. It looks like an issue when waiting for the pong response

```

// Finally wait for the pong response
/* msg, err := conn.WaitForResponse(timeout, 0)
if err != nil {
t.Fatalf("FAIL: Error waiting for response: %v", err)
}
switch msg := msg.(type) {
case devp2p.Pong:
t.Logf("INFO: Received pong response: %v", msg)
default:
t.Fatalf("FAIL: Unexpected message type: %v", err)
}/

[Gabriel-Trintinalia]

Fixed by #5955