Issue with Published and Draft Versions When Updating Related Components in Strapi v5
### Node Version

20

### NPM/Yarn/PNPM Version

9.6.7

### Strapi Version

5.7.0

### Operating System

Linux (Debian/Ubuntu)

### Database

PostgreSQL

### Javascript or Typescript

Javascript

### Reproduction URL

_No response_

### Bug Description

In Strapi v5, there is a critical issue with the published and draft version functionality, specifically when dealing with components inside related collections.


### **Problem:**

- After publishing the **component**, the **page** correctly displays the updated **component** in the CMS interface.
- However, when calling the API, the "Published" version of the **page** does not return the **updated component** (in fact, the component disappears from the response).
- The only way to fix this is to access the **page**, perform **unpublish**, and then **publish** again. Only then does the **updated component** appear in the API response.


### **Impact:**

This bug directly affects any system relying on the Strapi v5 API to correctly display updated content, requiring manual work to fix the inconsistency.


In cases of many collections and relations link in company that I work (Stone Co) this is a critical problem.

### Steps to Reproduce

### **Scenario:**

1. Create two collection types:
   - **pages**
   - **components**
2. Inside **pages**, use multiple **components** through a relation field.
3. Create a **page** with a related **component**.
4. Unpublish the **component** content and publish it.

### **Example:**

1. Create a **collection type pages** with a relation field for **components**.
2. Create a **page** and associate a **component** with it.
3. Publish both the **page** and the **component**.
4. Unpublish the **component** and publish it again.
5. Query the API in the "Published" version and observe that the **component** has disappeared.
6. Perform **unpublish** and **publish** on the **page** to temporarily fix the issue.


### Expected Behavior

- When a **component** is updated and published, any **page** referencing it should automatically reflect the update without requiring manual republishing.
- The **component** should not disappear from the API response in the "Published" version.

The logic for updating and propagating the publication of related components should be reviewed to ensure changes are correctly reflected without requiring manual republishing of each **page**.


### Logs

```shell

```

### Code Snippets

_No response_

### Media

_No response_

### Additional information

_No response_

### 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).