Integrate modelprop tsunami wrapper into docker compose files

[nbrinckm]

This is the change to include the modelprop for the tsunami case.

We had already had a lot of stuff prepared, so that it looks like it could work:

• There was already a seperate ModelpropTsWrapper that has default constraints to use Medina & Suppasri Schemas.
• The constraint management already seperates the Modelprop for earthquakes & tsunamis as it works on the wrapper name (eq-modelprop vs ts-modelprop).
• The deus wrapper already filters for modelprop results that are done with the earthquake schemas (currently only sara).

So as far as I can see the only thing that was needed was to adjust the docker-compose files:

• rename the modelprop container name (so that we know it is the earthquake specific one)
• add the wrapper for the tsunami modelprop.
• rename the input & output topics for those wrappers.

Things still todo:

• [ ] test with the frontend
• [ ] eventually adjust the input topcis for the tsunami modelprop so that we only call it after we run the tsunami run

[MichaelLangbein]

For testing with frontend: we could either ...

• ... merge https://github.com/riesgos/async/tree/issue80-include-new-wrappers-in-order-form-in-frontend into this branch to test if it works properly
• ... merge this branch into main and do the testing with frontend in this pr: https://github.com/riesgos/async/pull/85

I'd lean towards the latter: this way we can soon close this particular issue and make integration a separate issue. I figure that many small issues are more focussed than few big ones.

[MichaelLangbein]

Just for the completeness:

I wondered about listening to the tsunami service before this here starts. But there is really no constraint that would require to wait.

I guess if it's not required, we might as well leave it out, right?