QGrpcHttp2Channel: reject all reserved metadata keys from user metadata


The header-build path filtered only a hand-picked list of reserved keys.
Anything else reserved by HTTP/2 or gRPC: te, user-agent, grpc-timeout,
grpc-status, grpc-message and friends was forwarded directly and could
clash with the values the transport sets itself.

Drop user-provided keys by prefix (':' for HTTP/2 pseudo-headers,
'grpc-', 'qtgrpc-' for (Qt)Grpc reserved) plus the remaining transport-owned names (te,
content-type, user-agent), and log the drop so callers can spot the
mistake.

Update the documentation for the shared snippet accordingly.

Ref: https://grpc.github.io/grpc/core/md_doc__p_r_o_t_o_c_o_l-_h_t_t_p2.html

[ChangeLog][QtGrpc][QGrpcHttp2Channel] User-provided metadata with
reserved HTTP/2 or gRPC keys is now dropped when building requests to
avoid conflicts with transport-managed headers.

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