mri scan type PATCH fix

[HachemJ]

Brief summary of changes

This PR fixes a flaw in logic with the UPGRADE SQL patch for the 27 version.
This is the error I was getting when running the following CHANGE command:

ALTER TABLE `mri_scan_type`
  CHANGE `ID` `MriScanTypeID` int(11) unsigned NOT NULL auto_increment;

ERROR 1846 (0A000): ALGORITHM=COPY is not supported. Reason: Columns participating in a foreign key are renamed. Try ALGORITHM=INPLACE

I tried bypassing this error by dropping the foreign keys of the table and re-adding them with the renamed table columns.

This resulted in an additional error further along the release patch because one of the three foreign keys that were needed to be dropped in order to bypass the first error is dropped later on in the patch:

ALTER TABLE `mri_protocol_checks`
  DROP FOREIGN KEY `FK_mriProtocolChecks_ScanType`,
  ADD CONSTRAINT `FK_mri_protocol_checks_scan_type`
    FOREIGN KEY (`MriScanTypeID`) REFERENCES `mri_scan_type` (`MriScanTypeID`);

[MaximeBICMTL]

I checked the LORIS 26 SQL schema and this looks to be the only foreign key on Scan_type so the fix looks correct to me.

I also ran the corrected 26.0 to 27.0 patch on a fresh 26.0 Raisinbread install on my LORIS VM.