PeerDAS: lodestar does not work well with other clients

[twoeths]

Describe the bug

this metric shows lodestar node can only works well with other lodestar nodes

Expected behavior

should have diversified clients on this metric

Steps to reproduce

No response

Additional context

No response

Operating system

Linux

Lodestar version or commit hash

peerDAS

[twoeths]

looks like we always have invalid sequence number provided error with Prysm

May-21 23:01:40.634[network]       ^[[36mverbose^[[39m: Req  error method=ping, version=1, encoding=ssz_snappy, client=Prysm, peer=16...q3sHUi, requestId=439005, status=1, errorMessage= sNaPpY$^\invalid sequence number provided
Error: RESPONSE_ERROR_INVALID_REQUEST:  sNaPpY$^\invalid sequence number provided
    at responseDecodeSink (file:///usr/src/lodestar/packages/reqresp/lib/encoders/responseDecode.js:43:23)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async sendRequest (file:///usr/src/lodestar/packages/reqresp/lib/request/index.js:108:13)
    at async ReqRespBeaconNode.sendRequest (file:///usr/src/lodestar/packages/reqresp/lib/ReqResp.js:110:13)
    at async collectExactOneTyped (file:///usr/src/lodestar/packages/beacon-node/lib/network/reqresp/utils/collect.js:10:22)
    at async PeerManager.requestPing (file:///usr/src/lodestar/packages/beacon-node/lib/network/peers/peerManager.js:418:31)

[twoeths]

there are also TTFB_TIMEOUT with client NA

that error is deprecated, need to implement https://github.com/ethereum/consensus-specs/pull/3767/files

[twoeths]

this is due to #7879

it's not an issue in fusaka-devnet-0 after we roll up a fix for it