CANCEL_PUSH frames are always rejected on the frontend side as haproxy
never emits PUSH_PROMISE frames.
Rejection must also be performed systematically on the backend side as
haproxy never emits MAX_PUSH_ID frames, hence any push IDs mentionned by
the server are invalid.
The outcome is the same on both sides: the connection is closed with
H3_ID_ERROR and a glitch is accounted.