Validate and Bound Incoming Message Sizes [MED]

[HayimShaul]

Description
Before processing any inbound message -- signature replies, auditor payloads, or distribution acks -- enforce a maximum message-size limit and reject oversized or malformed payloads immediately. This prevents a responder from forcing the view to allocate unbounded memory for deserialization or signature verification. Pair size checks with schema/format validation so that structurally invalid messages are dropped at the earliest possible point in the pipeline.

Short Summary
Add max message size limits before deserializing signature replies, auditor payloads, distribution acks

[rovertrack]

hey @HayimShaul this seems interesting!
can i work on this?
Thanks

[AkramBitar]

Proposed fix is to add a max message-size check at the one place all inbound messages pass through (ReceiveRawWithTimeout), so signature replies, auditor payloads, and distribution acks are rejected before deserialization. Oversized payloads fail fast with ErrMessageTooLarge; malformed ones are still caught by the existing envelope validation. Default limit 100 MiB, configurable.