Updating a relation on an non-DP gets lost in the edit view
## Bug report

### Required System information

- Node.js version: 20
- NPM version: yarn 1.22
- Strapi version: 5.3
- Database: sqlite
- Operating system: macos
- Is your project Javascript or Typescript: js

<!-- Did you know you can run `yarn strapi report` or `npm run strapi report` to get this information easier? -->

### Describe the bug

I've hit the use case where a relation disappears in the UI. I have a non-DP contentType (form submission) relating to a DP contentType (vehicle). When it's created, all is good. When I update the relation in the form submission (even setting it to the same vehicle documentId again), it will dissappear from the Edit View. It will get returned in the API call populate, it will be visible in the List VIew, but it's gone from the Edit View. 
Changing the form submission contentType to DP makes the relation show up again.
So there is something wrong/missing/off in setting these relations for the Edit View.

### Steps to reproduce the behavior

1. Have a non-DP contentType relate to a DP contentType
2. Create items with relations
3. Update the non-DP contentType via REST
4. See that it shows up in the list view but not in the edit view

### Expected behavior

Relations should be visible in the edit view

### Additional context

I've been working a lot with Alexandre on non-DP relations in https://github.com/strapi/strapi/issues/21382 and https://github.com/strapi/strapi/issues/21355 so he would probably be interested in this issue