Report the compression algoritm to the Consumers

[eolivelli]

From an observability perspective it would be very useful to have some system jms properties that represent the compression algorithm used for each message.

We could implement this by adding some X-PulsarCompression property while consuming the message (and in QueueBrowser)

This property is not expected to be available for selectors.

It is better to not materialize this property on the producer side, as it will add costs, both as storage and both for the server side processsing of selectors.