A change inside the source changes the status to modified. Publishing a translation will publish the source too
### Node Version

20.18.3

### NPM/Yarn/PNPM Version

10.8.2

### Strapi Version

5.10.2 (80103017ad0134c4681c5b742cfd24091a839446)

### Operating System

MacOS

### Database

SQLite

### Javascript or Typescript

Typescript

### Reproduction URL

N/A

### Bug Description

👋 

When we make a change inside the source (en), it changes its status to _modified_, same for the translations (_as a side effect_). 

Now if we load a translation, and we publish it, it's going to publish the source too (_with our changed content_).

### Steps to Reproduce

1. Create a page with a translation
2. Make a change ex: a new keyword
3. Save
4. Its status =  `modified` same for the translated document
5. Load the translated document and publish it
6. Both are now `published` the translations as it should but the source too (_with the changes_)

### Expected Behavior

Keep the source as modified, when I publish a translation I don't publish the modified source. We can ex: hotfix the translated page, yet the changes inside the source don't need to be published.

The issue is created via https://github.com/strapi/strapi/blob/develop/packages/plugins/i18n/server/src/bootstrap.ts#L54 idk if it's expected.

I tried to remove it, and it seems to work. When I make a change to the source, the translations are still `published`. So I can't publish by mistake the source. Even if I do it via the API.


### Logs

```shell

```

### Code Snippets

_No response_

### Media

_No response_

### Additional information

Maybe we need another status, idk. But publishing a translation should _not_ trigger a published source too. Our changes should still be as a draft.


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