Add MessageType support for DLQ and AMQ telemetry #50
Description
There are many use-cases when we need to know which message is poisoned. This is extremely useful in the scenarios when one subscriber handles events from different domains and aggregates them. Given the fact that we have some events failing due to concurrency issues (EventSourcing package), it is not clear if the failed messages are failed because they were poisoned or just there was some transient problem which leads to a lot of confusion analyzing the telemetry.