Schema fixing: Optimise the structure of the ImageQualityIndicators table about ispyb-database-modeling HOT 3 OPEN

We are not using this table any more but we still have data inside so as far as modifications are compatible with the current structure will be fine with us.

However as the relation between ImageQualityIndicators and datacollection is via Image table , this will not work for us as it is today:
ADD PRIMARY KEY (dataCollectionId, imageNumber);

We are not filling dataCollectionId and imageNumber

from ispyb-database-modeling.

We had to go ahead with these changes in order to cope with increased insert rates. After the change (during the last shutdown) the problems previously seen have gone away. Going forward, we may still have to implement further changes to cope with the increasing size of the table.

We don't use the Image table any more, so for us the relation is directly from IQI to DC.

from ispyb-database-modeling.

We have to discuss it internally : perhaps we do not need any more the old data in these tables and could remove them and we have to see how it will behave with the proposed changes.

from ispyb-database-modeling.