Hierarchical logging

Currently logs from models have no direct reference to the parent task i.e.

<RAMSIS-SFMW> 2019-07-15T12:57:13+0000 DEBUG ramsis.sfm.worker.task 21425 task.py:57 - [<Task(id=d2b1a64a-f640-4583-bba3-cdbc0d2cdfd4)>] Executing <Model(name=EM1)> (args=d2b1a64a-f640-4583-bba3-cdbc0d2cdfd4, kwargs={}) ...
<RAMSIS-SFMW> 2019-07-15T12:57:13+0000 DEBUG ramsis.sfm.worker.model_sass 21425 model.py:56 - [<Model(name=EM1)>] Running model ...
<RAMSIS-SFMW> 2019-07-15T12:57:13+0000 DEBUG ramsis.sfm.worker.model_sass 21425 model.py:57 - [<Model(name=EM1)>] Importing input parameters ...
<RAMSIS-SFMW> 2019-07-15T12:57:13+0000 DEBUG ramsis.sfm.worker.model_sass 21425 model.py:59 - [<Model(name=EM1)>] Importing seismic catalog ...
<RAMSIS-SFMW> 2019-07-15T12:57:13+0000 DEBUG ramsis.sfm.worker.model_sass 21425 model.py:63 - [<Model(name=EM1)>] Received seismic catalog with 2 event(s).

For debugging purposes approach implementing an hierarchical solution e.g.

<RAMSIS-SFMW> 2019-07-15T12:57:13+0000 DEBUG ramsis.sfm.worker.model_sass 21425 model.py:56 - [<Task(id=d2b1a64a-f640-4583-bba3-cdbc0d2cdfd4)>][<Model(name=EM1)>] Running model ...

would be much better.