fix(files_trashbin): Fix size propagation when moving file to trash

[provokateurin]

Broken since #48224.
Checking if the source path is in the cache always returns false, because the file was already moved to a different path.
So any file that was trashed, did not update the parent folder sizes.

[provokateurin]

/backport to stable32

[provokateurin]

/backport to stable31

[come-nc]

Thanks a lot!
Any chance we can add a test to catch the issue next time?

[icewind1991]

Could you add some tests for this, With the object store cache behavior being different it would be good to ensure that both behaviors are tested.

[provokateurin]

Added a test and also confirmed that this was only broken for S3 before and now it works for local and S3 storage.

[AndyScherzinger]

/backport to stable31

[backportbot]

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

# Switch to the target branch and update it
git checkout stable31
git pull origin stable31

# Create the new backport branch
git checkout -b backport/54950/stable31

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick b36af651

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/54950/stable31

Error: Failed to push branch backport/54950/stable31: remote: Invalid username or token. Password authentication is not supported for Git operations.
fatal: Authentication failed for 'https://github.com/nextcloud/server.git/'

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

[provokateurin]

/backport to stable31

[juliusknorr]

/backport to stable30