Add diffractionplanid to datacollection and containerqueuesample

[stufisher]

I would like to add diffractionplanid to datacollection and containerqueuesample. This will allow us to know which diffraction plan has been queued and which diffractionplan a datacollection came from.

ALTER TABLE `DataCollection` 
    ADD `diffractionPlanId` INT UNSIGNED NULL DEFAULT NULL,
    ADD CONSTRAINT `DataCollection_ibfk9`
        FOREIGN KEY (`diffractionPlanId`)
            REFERENCES `DiffractionPlan`(`diffractionPlanId`)
                ON DELETE NO ACTION ON UPDATE NO ACTION;

ALTER TABLE `ContainerQueueSample` 
    ADD `diffractionPlanId` INT UNSIGNED NULL DEFAULT NULL,
    ADD CONSTRAINT `ContainerQueueSample_ibfk3`
        FOREIGN KEY (`diffractionPlanId`)
            REFERENCES `DiffractionPlan`(`diffractionPlanId`)
                ON DELETE NO ACTION ON UPDATE NO ACTION,
    ADD `blSampleId` INT(10) UNSIGNED NULL DEFAULT NULL,
    ADD CONSTRAINT `ContainerQueueSample_ibfk4`
        FOREIGN KEY (`blSampleId`)
            REFERENCES `BLSample`(`blSampleId`)
                ON DELETE NO ACTION ON UPDATE NO ACTION;

[KarlLevik]

• Combine changes to the same table in a single ALTER TABLE statement to avoid unnecessary extra table rebuilds with older versions of MariaDB/MySQL.
• Naming of FK constraints: Use the table name + underscore + fk1, fk2, ..., fkn. (Only because that is the unwritten convention I've been following ...)
• Maybe NO ACTION is better than RESTRICT. If for whatever reason the DiffractionPlan row is deleted, then we want the DataCollection(s) and ContainerQueueSample(s) to remain.

[stufisher]

@KarlLevik note i added blsample to containerqueuesample here so it can be used to queue samples, and subsamples. These are all related to each other so i think this is ok