Seppuku

Track error occurrences and shutdown service instance once a defined number of unique messages have errors in a defined time period.
I see your point, although I think the use cases are a bit different since theres 2 or 3 classes in consuming depending on which approach you configure. I could see adding the adapter namespace between consuming and rabbitmq/kafka to make it a bit more semantic

```ruby
Emque::Consuming::Adapter::RabbitMq::Manager
# etc ...
```