Handle remote paths with special characters correctly

[i2h3]

If files or folders contain characters with special treatment in URLs (such as ?, # or %), it may sabotage the metadata lookup because the paths were not parsed correctly yet.

[i2h3]

/backport to stable-4.0

[Copilot]

Pull request overview

This pull request aims to fix the handling of remote file paths that contain special characters (particularly # and ?) which are normally treated as URL delimiters. The implementation attempts to parse these characters as literal parts of file/directory names rather than as URL fragments or query parameters.

Changes:

• Modified the URL parsing logic in FilesDatabaseManager.itemMetadata(account:locatedAtRemoteUrl:) to extract paths from raw URL strings
• Added test cases for paths containing hashtags and question marks in directory names

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
FilesDatabaseManager.swift	Refactored URL parsing to treat special characters (#, ?) as literal characters in paths rather than URL delimiters
FilesDatabaseManagerTests.swift	Added tests for finding items in directories with hashtags and question marks in their names

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

Artifact containing the AppImage: nextcloud-appimage-pr-9341.zip

Digest: sha256:088d32f8a3b5a07c7182e7448bb4508280b60e185ecc0e6b4fc528e3288ff43b

To test this change/fix you can download the above artifact file, unzip it, and run it.

Please make sure to quit your existing Nextcloud app and backup your data.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud