Deleting files in deaccessioned datasets

What steps does it take to reproduce the issue?
On the tombstone page for a deaccessioned dataset users can select files using the checkboxes and attempt to "delete" files using the "Edit files" dropdown menu. This results in an error: "The selected files could not be deleted"; and a warning: "Info – The "DRAFT" version was not found. This is version "2.0""

• When does this issue occur?
  When a user attempts to delete a file in a deaccessioned dataset by selecting the file and clicking "Edit files" --> "Delete"

• Which page(s) does it occurs on?
  The tombstone page for a deaccessioned dataset.

• What happens?
  User receives an error message and a warning message (see above screenshot).

• To whom does it occur (all users, curators, superusers)?
  All users with sufficient permissions to edit datasets, including superusers.

• What did you expect to happen?
  Files to be deleted.

Which version of Dataverse are you using?
Harvard Dataverse 5.11.1 & Demo Dataverse 5.11.1 build 1069-02e3e92

Any related open or closed issues to this bug report?
8037 is describing the same bug (or feature?) and looking for a similar resolution (for users to be able to delete files) for a different use case.

6925 is describing a similar error in 4.20.

Start by reproducing the failure on the tombstone page for a deaccessioned dataset using the Edit files > Delete flow, then read related issues 8037 and 6925. Trace the deletion and version-selection handling for Dataverse 5.11.1. Done means authorized users can delete selected files without the error or the incorrect DRAFT-version warning.