[BUGFIX] Problem with no forecast returned

The issue was that multiple seismicitymodelrun rows were being create with rows without task_id. This meant that the row related to the result was not associated with the task_id, so no forecast was being returned.

The fix is to merge the seismicitymodelrun objects so that the data is added to the existing one.

There is also a change to create all the tables in the db, rather than only the ones that are used. This because there are no drawbacks to having empty tables, and if we want to use these tables in the future there will be no need for migration. Also possible to use ramsis-ws as database matches ramsis db (not that I see use case for this).