Resolve "persistent MQTT messages"

Closes #79 (closed)

Suggestion for testing:

• start with docker-compose-dev(.example).yml to mount dispatcher into workers and extractor into basic-demo-scheduler
  • checkout this tsm-orchestration branch 79-persistent-mqtt-messages
  • checkout tsm-dispatcher branch 29-persistent-mqtt-message (or use DISPATCHER_IMAGE_TAG=29-persistent-mqtt-message)
  • checkout tsm-extractor branch 31-mqtt-message-persistence
• stop all workers

go through all the workers by generating the respective mqtt messages

thing_creation

• populate frontend (e.g. with ./tsm-workflow populate from tsm-dev-tools)
• restart thing_creation workers (...db_setup, ...object_storage_setup, ...frost_setup, ...mqtt_user_creation, ...grafana_dashboard)
• check whether they received a message

object_storage_notification

• upload a file to minio bucket (e.b. with ./tsm-workflow upload)
• restart worker-file-ingest
• check whether message was received

data_parsed

• if data was parsed successfully, the extractor should send a notification to topic data_parsed
  • check basic-demo-scheduler logs whether data was parsed successfully
• restart worker-run-qaqc
• check whether message was received

user_login

• log in to frontend via helmholtz aai
  • might need to to remove all data, otherwise there could be a conflict with user groups in the frontenddb
• restart worker-grafana-user-orgs and check for message

I hope all works as expected