Bug: Non-latin1 filenames broken when using End-to-End Encryption

[MrDrups]

Description

When uploading files with Cyrillic filenames and enabling End-to-End Encryption, the filename is displayed incorrectly (garbled symbols) on the download page.

1. File contents are encrypted/decrypted correctly.
2. The issue only affects the filename display and download link when encryption is enabled.
3. On other pages (without E2EE), filenames display normally.
4. There is no problem with filenames without E2E Encryption.

Steps to Reproduce

1. Enable End-to-End Encryption (used level 3 encryption).
2. Upload a file with a Cyrillic filename (e.g., тестовый_файл.txt) through the web interface.
3. Open the download page.
4. Observe that the filename appears corrupted (unreadable symbols).

Tested with Docker version and Native deployment.

[Forceu]

Thank you very much for the bug report! Apparently this happened to all non-latin characters, fixed in b6799af