Explore the use of async RabbitMQ channels

[dillu24]

Rationale

At the moment we are using RabbitMQ with blocking channels. This means that any subscriber component is busy waiting for data until this data is received. As described in #277 this means that we cannot continuously send heartbeats from a component unless we make it threaded.

Therefore, the aim of this ticket is to explore whether it would be beneficial to use RabbitMQ in an asynchronous way.

For ticket closure

The outcome of this task is a document on confluence discussing the advantages/disadvantages of having RabbitMQ in an asynchronous fashion.