Performance regression since migration from strapi v4.25.12 to strapi v5.6.0
### Node Version

20.18.1

### NPM/Yarn/PNPM Version

10.8.2

### Strapi Version

5.6.0

### Operating System

Linux (Other)

### Database

PostgreSQL

### Javascript or Typescript

Typescript

### Reproduction URL

_No response_

### Bug Description

We’ve migrated from strapi  v4.25.12 to strapi v5.6.0 and quickly notice big performances regressions.

P95 latency on strapi/node was multiplied by a factor 5 (while requests are stable) : 
![Image](https://github.com/user-attachments/assets/497fa919-10af-4e25-af5d-071e32d6c58e)

We also found a lot more SQL requests to postgresql database and also an increase in latency : 
![Image](https://github.com/user-attachments/assets/78ed26b9-9316-4f24-8716-662f0725f086)

# Database investigation

While investigation the database, I found out that a single `PUT` on 2 fields generates a lot of deletions and creations in several tables in v5 while only generating one single update in v4 in one table : 

## In v4

```
curl -v -X PUT -d '{"data":{"views":"61718","likes":"691"}}' \
-H "Accept: application/json; charset=utf-8" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $TOKEN" \
"$HOST/api/blog-post-pages/26"
```
Impact in database before / after the request : 1 update

![Image](https://github.com/user-attachments/assets/f6f7b370-076c-4d1f-9676-29eade8b1228)

SQL query : `SELECT relname, n_tup_ins,  n_tup_del, n_tup_upd FROM pg_stat_user_tables order by n_tup_ins desc;`

## In v5
```
curl -v -X PUT -d '{"data":{"views":"61718","likes":"691"}}' \
-H "Accept: application/json; charset=utf-8" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $TOKEN" \
"$HOST/api/blog-post-pages/a6kii16k3zfiarwf1737m2h2"
```

Impact in database before / after the request : a lot of deletion and creation in multiple table linked to the blog-post-pages

![Image](https://github.com/user-attachments/assets/01fdcbc5-8d6c-416f-8747-eeefadb75c26)

## Conclusion 

This explains more SQL queries and could also explain performances regressions.

### Steps to Reproduce

1. create a content referencing other components and dynamic zones (like [structure-blog.zip](https://github.com/user-attachments/files/18503803/structure-blog.zip))
2. create several entries
3. inspect database via `SELECT relname, n_tup_ins,  n_tup_del, n_tup_upd FROM pg_stat_user_tables order by n_tup_ins desc;` and keep results
4. do a PUT request to update a field on component (not in a dynamic zone or relation)
5. launch again the SQL request and compare with previous results
6. notice multiple creations and deletion in multiples tables since last PUT request

### Expected Behavior

A PUT on field’s component should only generate a single UPDATE, like on Strapi v4 where a single UPDATE was executed.

### Logs

```shell

```

### Code Snippets

Here’s our blog structure :  [structure-blog.zip](https://github.com/user-attachments/files/18503803/structure-blog.zip)

### Media

_No response_

### Additional information

We’ve upgraded to 5.8 but the issue remains.

### Confirmation Checklist

- [x] I have checked the existing [issues](https://github.com/strapi/strapi/issues) for duplicates.
- [x] I agree to follow this project's [Code of Conduct](https://github.com/strapi/strapi/blob/develop/CODE_OF_CONDUCT.md).