Add includeDeaccessioned param to compare dataset versions API endpoint

[ekraffmiller]

For the compare dataset versions endpoint, we need to add a includeDeaccessioned param, similar to the get dataset version endpoint. This is needed for the SPA, for the use case where the latest-published version has been deaccessioned.

[sekmiller]

{
  "status": "OK",
  "data": [
    {
      "id": 886,
      "versionNumber": "3.0",
      "summary": "versionDeaccessioned; There is identifiable data in one or more files. Deaccessioning for testing purposes",
      "contributors": "Dataverse Admin",
      "publishedOn": "2025-03-17"
    },
    {
      "id": 885,
      "versionNumber": "2.0",
      "summary": {
        "Citation Metadata": {
          "Description": {
            "added": 0,
            "deleted": 0,
            "changed": 1
          },
          "Author": {
            "added": 1,
            "deleted": 0,
            "changed": 0
          }
        },
        "Additional Citation Metadata": {
          "added": 2,
          "deleted": 0,
          "changed": 0
        },
        "files": {
          "added": 0,
          "removed": 0,
          "replaced": 0,
          "changedFileMetaData": 0,
          "changedVariableMetadata": 0
        },
        "termsAccessChanged": true
      },
      "contributors": "Dataverse Admin",
      "publishedOn": "2025-03-17"
    },
    {
      "id": 884,
      "versionNumber": "1.0",
      "summary": "firstPublished",
      "contributors": "Dataverse Admin",
      "publishedOn": "2025-03-17"
    }
  ]
}

I don't think we need to add an "includeDeaccessioned" parameter. In the jsf version even guest users are able to see deaccessioned versions on the version list. The differences are not available to users regardless of their permissions. We do include the deaccession reason and notes.

[sekmiller]

I do have to update the logic to get the deaccessioned versions to show up in the list.