Get ROR data in JSON format, find the right file using admin.schema_version from JSON records, handle ROR data update failures gracefully

[bozana]

From the suggestions from the ROR team we should implement the following in this issue:

• use JSON instead of CSV -- JSON is ROR's canonical data format, used internally for all operations. The CSV, by contrast, is a derived convenience format, intended for users doing manual review of the data or who are otherwise unable to work with the JSON. ROR's data fields are also inherently hierarchical and the CSV flattens these structures into a best approximation.
• handle Zenodo API failures gracefully (timeouts, unexpected response formats, changed field names) -- the Zenodo API has had in the past undocumented instability and behavior changes, so this dependency needs safeguarding.
• read admin.schema_version from JSON records, and use that schema version to determine compatibility and to find the right JSON file, instead of relying on file names.
• ensure that ROR data update script never breaks OJS functionality, in this case installation.