[Bug]: AWS-S3 > moving data between shares of different accounts > data corruption

### ⚠️ Before submitting, please verify the following: ⚠️

- [x] This is a **bug**, not a question or a configuration issue.
- [x] This issue is **not** already reported on Github (I've searched it).
- [x] Nextcloud Server and Desktop Client are **up to date**. See [Server Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) and [Desktop Releases](https://nextcloud.com/install/#install-clients) for supported versions.
- [x] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/)

### Bug description

I have an uptodate nextcloud setup (30.0.4) running AWS S3 as main data storage.

Moving a file in my Windows shared folder results in data corruption!

### Steps to reproduce

1. Set up a maiden Nextcloud setup with AWS-S3 as main storage
2. Create two users
3. Create a shared folder in User 'B' for user 'A'
4. use the windows desktop app to create a cloud drive, using user 'A'
5. place a file somewhere (NOT in the share)
6. move the file to the shared folder

Mayhem!

There is a a 'urn:oid:...' for the new user, but the file is of zero size.
In the web interface I do see the image preview of the file.
[update]But downloading is impossible[/update]

So I am expecting a "owner transfer" is attempted, but failed somehow. In the AWS-S3 structure that would be ideal, using the same urn:oid would be the nicest way to do this.. but something is clearly going wrong!

This bug makes moving files in AWS-S3 from and to shares extremely dangerous!

### Expected behavior

just move the file!

### Which files are affected by this bug

files being moved from and to a shared folder

### Operating system

Windows

### Which version of the operating system you are running.

Windows 10

### Package

Official Linux AppImage

### Nextcloud Server version

30.0.4 (also in 29, and I'm quite sure this happened to me in 28 also)

### Nextcloud Desktop Client version

3.15.2

### Is this bug present after an update or on a fresh install?

Updated from a minor version (ex. 3.4.2 to 3.4.4)

### Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

### Are you using an external user-backend?

- [x] Default internal user-backend
- [ ] LDAP/ Active Directory
- [ ] SSO - SAML
- [ ] Other

### Nextcloud Server logs

```shell

```

### Additional info

_No response_