Media library not respecting changing S3 storage
## Bug report

### Required System information

- Node.js version: 22.11.0
- NPM version: 11.0.0
- Strapi version: 5.6.0
- Database: postgres
- Operating system: linux-x64
- Typescript

### Describe the bug

Changing the configured S3 bucket for the Media library does not change the location for existing images.
 - the card for each existing image in the media library now longer displays the thumbnail
 - the link for the image remains the same as the original bucket, not the new bucket.

**Surely, it should be possible to change the S3 storage.**

### Steps to reproduce the behaviour

Today, I tried to create a replica environment for testing.

I successfully created a test database by exporting from the production database and importing into the new test database (using Strapi export/import).

I then copied the contents of the S3 bucket containing the Media library images into a new S3 test bucket, and changed the S3 bucket for the media library in Strapi.  This cause the problem above.

### Expected behaviour

Changing the S3 bucket should result in Strapi using the new bucket.

### Screenshots

With original bucket (pcstrapi)
![image](https://github.com/user-attachments/assets/beb49cb2-1277-467e-8e60-4ea328648259)
copied link: https://pcstrapi.fra1.digitaloceanspaces.com/80431c102dc6f83fe4a0470e59fc8113.jpeg

With new bucket (pcstrapitest)
![image](https://github.com/user-attachments/assets/2fe2335f-ddd8-4672-8521-9db3bfe093a0)
copied link: https://pcstrapi.fra1.digitaloceanspaces.com/80431c102dc6f83fe4a0470e59fc8113.jpeg

In the latter case, the copied link should be https://pcstrapitest.fra1.digitaloceanspaces.com/80431c102dc6f83fe4a0470e59fc8113.jpeg

### Code snippets



### Additional context


