consumer: BaseConsumer is prepared to handle only one action

[diegodelemos]

Right now, the BaseConsumer class is prepared to handle only one action. It is possible that in the near future we will have to consume from multiple queues and therefore perform different actions accordingly.

There are at least two options, that I can see now, to implement this:

• Follow how Celery uses kombu.ConsumerMixin, which can be seen here. Basically, the ConsumerMixin class takes a mapping with the different types of messages and the different actions, so depending on the message type a concrete function is called

• Use the ConsumerMixin as a Consumer runner which contains different ConcreteConsumers for different use cases like JobStatus, WorkflowLogs, FilePullStatus. For doing this there might be a limitation since by default ConsumerMixin uses the kombu.Consumer class, see here, so we might need to reimplement it.