IQSS/11142 show replace in file differences

[qqmyers]

What this PR does / why we need it: On the file page, the version table did not show when one file replaced another (it just showed No changes associated with this version. Now it shows:

Which issue(s) this PR closes:

• Closes Changes in file do not show up in File version history #11142

Special notes for your reviewer: The fix for this was rather trivial, just turning on existing functionality by adding a details=true flag. However, in fixing that I discovered:

• that adding free-form provenance to a file causes the dataset version table and difference api to fail due to a null pointer - I fixed that in this PR,
• that despite being almost the same code, there is a separate FileVersionDifference class that is called from the FilePage. W.r.t. the SPA, I think the code in the FilePage that figures out which FileMetadata/DataFile to compare will need to be moved to a new API call, but it might be possible to then just use the code in DatasetVersionDifference instead to allow the other class to be deprecated. I did not dig fully into this, so it's possible that there are other differences I missed,
• The file-versions.xhtml has several cut/paste ~errors from being copied from the dataset-level code. Things like the method in

  dataverse/src/main/webapp/file-versions.xhtml

  Line 45 in 6d6a509

  actionListener="#{FilePage.compareVersionDifferences()}">

  doesn't exist, the check at

  dataverse/src/main/webapp/file-versions.xhtml

  Line 53 in 6d6a509

  <p:column selectionMode="multiple" class="col-select-width text-center" rendered="#{DatasetPage.compareVersionsCount > 2}"/>

  references the DatasetPage, and the detailsBlocks referenced in

  dataverse/src/main/webapp/file-versions.xhtml

  Line 44 in 6d6a509

  oncomplete="PF('detailsBlocks').show();post_differences();"

  only exists on the dataset page. None of these appear to be fatal - but my guess is that they probably cause there to be no checkbox column through which one could compare two versions and see the details (hence the details flag). Doesn't seem like anything worth fixing given just using details=true in the table is probably good enough, but again the SPA might want to decide whether the file version table should work more like the dataset-level one than it does/can share more code, etc.

Suggestions on how to test this:
Create/publish a dataset with a file, replace the file, verify that the file page version table notes the change.
Add a free-form provenance note to the file, check that the save succeeds/the dataset page is still viewable, etc. (allowing free-form provenance is a flag that may need to be set on the test machine).

Does this PR introduce a user interface change? If mockups are available, please link/include them here: In the old table, a file that was replaced, and had a description change just shows as

• this is QDR so slightly different styling.

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

Additional documentation: