[mri_violations] Add new mri_protocol fields to "Could not identify scan type" page

[cmadjar]

Brief summary of changes

This adds the image_type, PhaseEncodingDirection and EchoNumber to the tables displayed under the page displayed after clicking on "Could not identify scan type" link in the main page.

Testing instructions (if applicable)

1. check out this branch
2. go to the MRI violation module and click on one of the "Could not identify scan type" link present in the violation table. That will redirect you to the page with the list of MRI protocol and list of fields for the violated scans. Ensure that there are image_type, PhaseEncodingDirection and EchoNumber (note: sometimes those fields will be empty if there is not restriction on the mri_protocol table for those fields or if the violated scan does not contain a PhaseEncodingDirection or multiple EchoNumber

Note: make sure to run the SQL patches that affect the MRI tables in the new patch directory

Link(s) to related issue(s)

• Resolves https://github.com/aces/HBCD/issues/231

[nicolasbrossard]

Code looks good. Tested on my VM and it works perfectly. 👍