Add support for Compression Dictionary Transport (RFC 9842)

[arturobernalg]

Implement dictionary negotiation, storage, matching, and dcb / dcz decoding

[ok2c]

@arturobernalg This is a lot of new code. I will scan it for obvious programming errors or inefficiencies. I, however, cannot do a proper review as far as its conformance to the RFC is concerned. I will have to trust you know what you are doing.

One question, though. Is there a reason this is an async only feature?

[arturobernalg]

One question, though. Is there a reason this is an async only feature?
@ok2c
No fundamental reason. I initially limited the implementation to the async execution chain because that was the use case I was targeting and the capture/decoding code was based on AsyncDataConsumer. The protocol itself is equally applicable to the classic client, so the classic execution chain should support it as well.

[ok2c]

@arturobernalg I must admit i do not quite understand what is going on here, but some bits, especially header parsing ones do not good enough to me. I cannot make a call on this change-set

[ok2c]

@arturobernalg Exactly

[ok2c]

@arturobernalg This could be done much, much more efficiently. You are parsing and copying header values into a comma delimited list and then parsing it again. Consider using MessageSupport#parseHeaders or MessageSupport#parseHeadersStrict instead.