Separate MQTT::Session from AMQP::Queue

[kickster97]

Is your feature request related to a problem? Please describe. Currently the MQTT::Session is inheriting AMQP::Queue, forcing some AMQP behaviours and characteristics on the MQTT::Session. This was done as a POC and works fine, but it puts constraints on the session.

Describe the solution you'd like The MQTT::Session should be a stand alone class with its own publish method, that does not need to be tied to a consumer class (Having the Client class should be sufficient for an MQTT connection since you can only have one consumer). Overall, breaking out the MQTT::Session would make the MQTT solution more efficient and easier to work with.

This issue is a WIP