fix(trashbin): Truncate long filenames

[Pytal]

Summary

Truncate filenames longer than the 250 char limit of the oc_filecache name column to fix deletion of files with names that would exceed 250 chars when appended with the 12 char timestamp suffix

Characters are removed from the middle of the string rather than the end due to dependencies on the embedded timestamp string which if truncated would throw trashbin errors

TODO

• Tests

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)

[szaimen]

@Pytal why not increase the table lenght instead?

[Pytal]

@Pytal why not increase the table lenght instead?

Common file system limits 🤷‍♂️

[icewind1991]

Looks good but could really use some tests

[Pytal]

Fixed tests!

[blizzz]

/backport to stable27

[blizzz]

/backport to stable26

[blizzz]

/backport to stable25

[blizzz]

/backport to stable24

[blizzz]

/backport to stable20

[backportbot-nextcloud]

The backport to stable25 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable25
git pull origin/stable25
# Create the new backport branch
git checkout -b fix/foo-stable25
# Cherry pick the change from the commit sha1 of the change against the default branch# This might cause conflicts. Resolve them.
git cherry-pick abc123
# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable25

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

[backportbot-nextcloud]

The backport to stable24 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable24
git pull origin/stable24
# Create the new backport branch
git checkout -b fix/foo-stable24
# Cherry pick the change from the commit sha1 of the change against the default branch# This might cause conflicts. Resolve them.
git cherry-pick abc123
# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable24

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

[backportbot-nextcloud]

The backport to stable20 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable20
git pull origin/stable20
# Create the new backport branch
git checkout -b fix/foo-stable20
# Cherry pick the change from the commit sha1 of the change against the default branch# This might cause conflicts. Resolve them.
git cherry-pick abc123
# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable20

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

[solracsf]

/backport to stable25

[Pytal]

/backport to stable24

[Pytal]

/backport to stable20

[backportbot-nextcloud]

The backport to stable20 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable20
git pull origin/stable20
# Create the new backport branch
git checkout -b fix/foo-stable20
# Cherry pick the change from the commit sha1 of the change against the default branch# This might cause conflicts. Resolve them.
git cherry-pick abc123
# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable20

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport