Downscore clients with SSZ_SNAPPY_ERROR_OVER_SSZ_MAX_SIZE error

[twoeths]

Describe the bug

Got a lot of errors like this

Jan-17 07:38:21.909[network]       verbose: Req  error method=metadata, version=2, encoding=ssz_snappy, client=Unknown, peer=16...pWVhz9, requestId=403654, code=SSZ_SNAPPY_ERROR_OVER_SSZ_MAX_SIZE, maxSize=17, sszDataLength=24
Error: SSZ_SNAPPY_ERROR_OVER_SSZ_MAX_SIZE

that only happens to "Unknown" client, I don't see we downscore them a lot, maybe we need to apply more penalties on them. If it happens a lot it may be disconnected by our peer manager heart beat

Expected behavior

I think this error is similar to "REQUEST_ERROR_INVALID_RESPONSE_SSZ", need to apply low tolerance there, i.e. ~5 occurrences will get the peer banned

Steps to reproduce

No response

Additional context

No response

Operating system

Linux

Lodestar version or commit hash

v1.14.0

[nflaig]

There is another, possibly related error I am seeing on my Lodestar node (v1.14.0-rc.1)

Jan-17 09:17:23.039[network]         error: Error setting agentVersion for the peer peerId=16Uiu2HAmKpgbkNA2AKYvt4qfdwFsSwuM7NwE8aMMHoMJiCBAxKAL - NotFound: 
Error: NotFound: 

[matthewkeil]

There is another, possibly related error I am seeing on my Lodestar node (v1.14.0-rc.1)

Jan-17 09:17:23.039[network]         error: Error setting agentVersion for the peer peerId=16Uiu2HAmKpgbkNA2AKYvt4qfdwFsSwuM7NwE8aMMHoMJiCBAxKAL - NotFound: 
Error: NotFound: 

Talking with @tuyennhv this is a separate error. I created issue #6365

[matthewkeil]

Fixed with #6366