Steps to reproduce

1.  Go to new assets app, select an already published asset and click on show versions action 
2.  Select one older version and click show
3. Click on Save changes

Expected results

Save changes button shouldn't be there as it happened in old assets app

Actual results

Save changes button appear which might be confusing for users and an error is thrown when pressing it

Workaround

Create a new detail subapp avoiding the commit action, then setting this new app in the version dialog by decorating /dam-app-jcr/dialogs/versions.yaml

Development notes

Perhaps this ticket should be moved to another project as this would happen not only in assets app but for every app setting detail subapp in version dialog. It would be good to make it work as in it did in Magnolia 6.1.