Add new RelativeIceThickness table

[HorstmannA]

We are trying to integrate a recent EM software into the data analysis pipeline. The software returns relative ice thickness values per micrograph, and we would like to store the results as a 5-figure summary. To do this, it would be useful to have a new table in ISPyB (I'm suggesting RelativeIceThickness, open to discussion) to store data for plots. It would be linked to the MotionCorrection table, similar to the CTF table. This table is experimental and might require changes in the future.

Draft schema:

CREATE TABLE RelativeIceThickness (
   'relativeIceThicknessId' int(11) unsigned NOT NULL AUTO_INCREMENT,
   'motionCorrectionId' int(11) unsigned DEFAULT NULL,
   'autoProcProgramId' int(11) unsigned DEFAULT NULL,
   'minimum' float DEFAULT NULL COMMENT 'Minimum relative ice thickness, Unitless',
   'q1' float DEFAULT NULL COMMENT 'Quartile 1, unitless',
   'median' float DEFAULT NULL COMMENT 'Median relative ice thickness, Unitless',
   'q3' float DEFAULT NULL COMMENT 'Quartile 3, unitless',
   'maximum' float DEFAULT NULL COMMENT 'Minimum relative ice thickness, Unitless',
   PRIMARY KEY ('relativeIceThicknessId'),
   KEY `RelativeIceThickness_fk_programId` ('programId'),
   KEY `RelativeIceThickness_fk_motionCorrectionId` ('motionCorrectionId'),
   CONSTRAINT `RelativeIceThickness_fk_programId`
     FOREIGN KEY (`autoProcProgramId`)
       REFERENCES `AutoProcProgram` (`autoProcProgramId`)
         ON DELETE NO ACTION ON UPDATE CASCADE,
     CONSTRAINT `RelativeIceThickness_fk_motionCorrectionId`
       FOREIGN KEY (`MotionCorrectionId`)
         REFERENCES `MotionCorrection` (`motionCorrectionId`)
           ON DELETE NO ACTION ON UPDATE CASCADE
 )