Add a Flyway script to sanitize any constraint-violating ContentType entries in DataFile table (for ex., CR)

but who would have carriage returns in their contenttype fields, you ask? why, we do, of course.

This only manifests when checksumvalue must be replaced in the database - if no replacement is required, the API returns:
{"status":"OK","data":{"message":"Datafile rehashing complete. datafile_id successfully rehashed. New hash value is: new_hash_value"}}

To reproduce:

=> update datafile set contenttype='application/x-sas-transport
'> ' where id='datafile_id;
=> update datafile set checksumvalue='' where id='datafile_id';

Then call /api/admin/computeDataFileHashValue/datafile_id/algorithm/MD5

Leonid notes that there are other installations as old as Odum's, so this could potentially come up again. He'd like a flyway script to clean up such contenttype entries.

No migration file is named. Start by locating existing Flyway migrations and the DataFile table definition, then review the supplied SQL reproduction and the computeDataFileHashValue endpoint behavior. Done means a Flyway migration cleans existing constraint-violating ContentType values, including carriage returns, without changing valid entries.