Feature/492 publish dataset with compare versions

[ekraffmiller]

What this PR does / why we need it:

This PR adds a use case for comparing dataset versions, and uses it to add a property to the Dataset object, a boolean that indicates whether the next version should be a major or minor version update.
The boolean requiresMajorVersionUpdate will be true if the draft contains added, removed or replaced files. If this boolean is true, then the PublishDatasetModal will include help text describing the major version update.

Which issue(s) this PR closes:

• Closes Publish Dataset: Only allow Major Version Update if files are added or removed #492

Special notes for your reviewer:

Suggestions on how to test this:

1. Create and publish a dataset.
2. Edit the metadata of the dataset, and click the Publish button. The PublishDatasetModal will show an option for choosing either minor or major version update.
3. Publish the dataset, and then create another draft version, with an uploaded, removed or replaced file.
4. Click the publish button again, and the PublishDatasetModal should display help text about the required major version update.

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

Is there a release notes update needed for this change?:

Additional documentation:

[coveralls]

coverage: 97.353% (+0.008%) from 97.345%
when pulling e2e050c on feature/492-publish-dataset-with-compare-versions
into 88d218a on develop.

[g-saracca]

Looks good, just some questions

[ekraffmiller]

thanks @g-saracca, ready to review now

[g-saracca]

Great job @ekraffmiller , approving!
Just one comment, you are mapping the js-dataverse versionDiff in toDatasetVersionDiff but not changing any property, maybe we don't need the mapper at all?

[ekraffmiller]

Great job @ekraffmiller , approving! Just one comment, you are mapping the js-dataverse versionDiff in toDatasetVersionDiff but not changing any property, maybe we don't need the mapper at all?

Thanks! Yes, I thought maybe we didn't need the mapper, but wanted to follow the convention used in the mapping logic. Feel free to remove it if you want.