Add file_embargo_end_date to public files if not already set

[tomwrobel]

If a fileset:

• has a file_made_available_date
• has a has_public_url
• has no file_embargo_end_date

Set the file_embargo_end_date to the file_made_available_date in the Sword2 response

[mrdsaunders]

Toby and I tested this morning and blank embargo release date didn't seem to automatically trigger excessive embargo.

So this won't do any harm, but I'm not sure it will fix the issue. I believe the issue is indefinite date being ingested to all files in SE data even where files have distinct dates (or not date). I'll put in ticket to AB.

[mrdsaunders]

AB confirms that blank embargo release date should not be ingested to SE as indefinite. So blank dates are not the issue. However date format may play a role here, so he is going to test this by adding date formatting to the crosswalk, we can then test.