QGrpcHttp2Channel: enforce frame size limit on outbound messages


The receive-side guard bounded incoming frames by both the wire-format
u32 length and qsizetype capacity, but the send path silently cast
data.size() to quint32 when writing the frame header, truncating
oversized payloads on the wire.

Move the cap into a GrpcMaxPayloadSize constant and reject outgoing
messages above it via asyncFinish with ResourceExhausted, mirroring the
inbound behavior.

[ChangeLog][QtGrpc][QGrpcHttp2Channel] Outgoing messages exceeding the
maximum frame size are now rejected with StatusCode::ResourceExhausted
instead of being silently truncated on the wire.

Pick-to: 6.11 6.8
Change-Id: I59ff23a6e5bbb5783fec52cc214789da89df852e
Reviewed-by: MÃ¥rten Nordheim <marten.nordheim@qt.io>
commitf764351a91e8d39172f483cc9173999c12778131
parent8c8f0e3cffa4003cd549a0a6761297f53e1a5f75
authorDennis Oberst <dennis.oberst@qt.io>
committerDennis Oberst <dennis.oberst@qt.io>
commit timeMon, 1 Jun 2026 14:55:41 +0000