In latest Dassie (Ruby 3.3, Rails 7.2), uploading a new version of a fileset does not change thumbnail or UV version

[nhomenda]

Descriptive summary

In latest Dassie (Ruby 3.3, Rails 7.2), uploading a new version of a fileset does not change thumbnail or UV version

Steps to reproduce the behavior in User Interface (UI)

• In Dassie (https://dev.nurax.samvera.org/)
• Navigate to the "Work View" page
• Click on the title of a file in the "Items" section
• Click the "Edit This File" button
• Click on the "Versions" tab
• Click on the "Choose File" button under the "Upload New Version" heading and select a new file
• Click the "Upload New Version" button. The screen will refresh with a success message
• The "User Activity" section should reflect the change to the file's version. Instead, the thumbnail and IIIF manifest show the old file, while the User Activity table lists new version activities and "Download image" provides the newest version.
• https://dev.nurax.samvera.org/concern/parent/9880vr22k/file_sets/rv042t46z
• https://dev.nurax.samvera.org/downloads/rv042t46z?locale=en

Acceptance Criteria/Expected Behavior

Uploading a new version of a file updates the work's thumbnail and IIIF manifest

[randalldfloyd]

As this is not being addressed for v5.1, here is an explanation for release notes:

For a "Wings" based work (i.e. Valkyrie models on Fedora 4), uploading a new version of a FileSet does not change the thumbnail or version displayed in the viewer. This is potentially related to #6998. It does work as expected for older ActiveFedora based works, as well as Valkyrie resources on Postgres and Fedora 6.