Fix interceptor chain traversal direction per hook type
Previously all interceptor hook points were traversed in the same
registration order, independent of whether the event belonged to the
outbound (App → Network) or inbound (Network → App) call path. This
effectively broke the logical interceptor pipeline model, where request
events and response events must flow through the chain in opposite
directions.
This change introduces the InterceptionFlow enum and associates each
hook type with its correct traversal direction via InterceptorInfo.
Outbound hooks are now executed in registration order, while inbound
hooks run in reverse order, forming a proper bidirectional middleware
pipeline.
This matches the canonical gRPC interceptor chaining semantics, where
requests pass “down” the chain and responses propagate back “up” through
interceptors in reverse order.
Ref: https://grpc.io/docs/guides/interceptors/
Found during the Qt 6.11 API review.
Pick-to: 6.11
Task-number: QTBUG-142670
Change-Id: I773e3ed2544061e3ac9802717ed2e4ffd0cc7b8f
Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>