Fix aliasing mimes

[skjnldsv]

Fix regression by #1273
Fix #1450

[skjnldsv]

/backport to stable25

[skjnldsv]

If we use the original handler instead of the registered aliases, we break all aliases on file opening.

[Raudius]

We could check again if the override handler is specified, if so we can use the original handler coponent?

const component = overrideHandlerId ? handler.component : this.components[mime];
this.currentFile = new File(fileInfo, mime, component)

[skjnldsv]

No, we should be consistent on how we do things for other File creations :)

viewer/src/views/Viewer.vue

Line 613 in bbcd4ef

this.currentFile = new File(fileInfo, mime, this.components[mime])

viewer/src/views/Viewer.vue

Line 637 in bbcd4ef

this.previousFile = new File(prev, mime, this.components[mime])

viewer/src/views/Viewer.vue

Line 647 in bbcd4ef

this.nextFile = new File(next, mime, this.components[mime])

[jkhsjdhjs]

Can confirm, this fixes the issue on my nextcloud 25.0.1 instance.

[Raudius]

Doesn't this revert the behaviour back to always use the viewer compontent based on mime type? This would then break the openWith method.

[ariselseng]

It would be nice if this can be worked on. My app camerarawpreviews has quite a few users, and currently does not work with Viewer. I know it did before though.
Here is my use of this feature: https://github.com/ariselseng/camerarawpreviews/blob/master/js/register-viewer.js
If you would do a rebase @skjnldsv I can certainly try it out locally and see if it helps.

[joshtrichards]

@ariselseng Right now this PR is set in draft mode so it's probably being overlooked for formal reviews.

Seems to have some positive feedback from testers, but also an outstanding question from @Raudius. I'm not familiar with this area of code so I don't feel qualified commenting one way or another.

@skjnldsv: This is your PR - thoughts? Okay to pull this out of draft? Need us find some more folks to test?