feat: Add forbidden_filename_basenames config option

[susnux]

• For 🪟📁📄 Ability to enforce windows compatible file names on the server #44963

Summary

This allows to configure forbidden filenames (the full filename like .htaccess) and also forbidden basenames like com0 where com0, com0.txt and com0.tar.gz will match. We need this as only using basenames was too restrictive and will cause problems on some systems when updating.

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)

[solracsf]

'forbidden_filename_basenames' => ['archive'],

This will also block Archive.2024.tar.gz

If the function remains as-is, where first dot defines the basename, this needs perhaps a better documentation (a warning ⚠️ ) about this behaviour so admin fully understand the risk. Or a refactor 😄

[susnux]

This will also block Archive.2024.tar.gz

Yes this is exactly what it should do, it is only for filtering basenames. Needed for Windows support as on Windows com0 and com0.tar.gz are both the same invalid filename (see windows namespaces).