Rate limit hit during fusaka devnet for uknown streams

### Describe the bug

Observed the following errors while analyzing the logs for the fusaka devnet-3.

This does not happen very often, I observed these twice in collections of logs I collected over night. We may investigate those later sometime.

```
2025-08-07T03:20:07.787Z libp2p:mplex rate limit hit when receiving messages for streams that do not exist - closing remote connection\n
2025-08-07T03:20:07.787Z libp2p:mplex:stream:initiator:1 abort with error Error: Too many messages for missing streams\n
at MplexStreamMuxer._handleIncoming (file:///usr/app/node_modules/@libp2p/mplex/dist/src/mplex.js:259:28)\n
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n
at async MplexStreamMuxer.sink (file:///usr/app/node_modules/@libp2p/mplex/dist/src/mplex.js:196:25)\n
at async Promise.all (index 0)\n
```
------

```
2025-08-07T03:20:36.842Z libp2p:mplex rate limit hit when receiving messages for streams that do not exist - closing remote connection\n
2025-08-07T03:20:36.842Z libp2p:mplex:stream:initiator:1 abort with error Error: Too many messages for missing streams\n
at MplexStreamMuxer._handleIncoming (file:///usr/app/node_modules/@libp2p/mplex/dist/src/mplex.js:259:28)\n
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n
at async MplexStreamMuxer.sink (file:///usr/app/node_modules/@libp2p/mplex/dist/src/mplex.js:196:25)\n
at async Promise.all (index 0)\n
```

### Expected behavior

The rate limit should not be set ever.

### Steps to reproduce

There are no exact steps for it.

### Additional context

We observed same issue earlier in the e2e tests, and solved those by increasing `disconnectThreshold`.

### Operating system

Linux

### Lodestar version or commit hash

peerDAS