fix(files): validate input when creating file/directory

[Antreesy]

• Resolves: [Bug]: 'forbidden_chars' not respected when creating File / Directory #46688

Summary

Before	After

TODO

• Review
• Compile
• Backport back to stable28

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[susnux]

There is common filename validation now with new nextcloud-files, this function will be removed until beta1 of Nextcloud 30 ;)

[Antreesy]

There is common filename validation now with new nextcloud-files, this function will be removed until beta1 of Nextcloud 30 ;)

I saw some PRs on this, but they're not backported, so - not coming to stable branches?
In that case I can rebase my PR directly on stable29 and continue from there

[susnux]

I saw some PRs on this, but they're not backported, so - not coming to stable branches?

Yes and no, the plan is to use the feature introduced here:
nextcloud-libraries/nextcloud-files#1013

This also works for Nextcloud 28 and 29. So we can use validateFilename in all supported versions and return user feedback based on the exception that is thrown. As it is too much work to maintain all three versions if they diverge too much :)

[Antreesy]

This also works for Nextcloud 28 and 29.

Got you there 😉

[susnux]

Lets go with this first, as there is a lot of good stuff!
I will then add the library stuff ontop of your changes.

Thank you!

[susnux]

/compile

[susnux]

/backport to stable29

[susnux]

/backport to stable28