Cap the potential spam for the max rate limit

[evan-forbes]

here we want to quantify the damage a single malicous peer can do with large rate limits then cap that impact somehow

in most spots this is fine and only annoying. there are known spots where this could start to cause slowdowns, especially with many malicous peers.

to avoid this, we can evaluate each message type and add stricter limits for when to disconnect. For example, ideally we'd disconnect upon any duplicate message, however due to issues with catch up or the mempool this is not possible to fully block. Therefore if we could recognize the issue and count, then we could set a very conservative limit and kick the peer should it cross that threshold

ref celestiaorg/celestia-app#6221