Support interaction with dead letter queues

[MichaelHancock]

Currently the dead letter queue name is not surfaced publicly by the abstractions project, and is an internal implementation detail. If a developer wished to interact with the dead letter queue they would need to rely on this detail, and could be caught out by changes to this implementation resulting in an unexpected breaking change.

The option to provide the dead letter queue name and/or behaviour (ie. full queue name, or appended to main queue name) could be provided which would both grant a developer full control around the dead letter queue allowing them to adapt to existing configurations, as well as surfacing the existing behaviour to the public API (documenting its usage).

Both ServiceBus and RabbitMQ share the concept of dead letter queues making this functionality an ideal candidate for abstraction.