Data export/import v4 -> v5 not creating draft record counterpart.
## Bug report

### Required System information

<!-- Please ensure you are using the Node LTS version (18, 20, or 22) -->
<!-- Strapi v3 is no longer supported, please update to Strapi v4 -->
<!-- If you are reporting a frontend bug please provide error logs after setting STRAPI_ENFORCE_SOURCEMAPS=true in your .env -->
<!-- This environment variable makes frontend errors easier to read and trace -->

- Node.js version: v20.10.0
- NPM version: 10.2.3
- Strapi version: 5.7.0
- Database: Postgres
- Operating system: OS: darwin-arm64 Sequoia 15.1
- Is your project Javascript or Typescript: Typescript

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

### Describe the bug

I am exporting data from a v4 Strapi instance and importing it into to a v5 Strapi instance. And all the records are in my database as they should, but are not visible in Strapi. I discoverd that this is caused by the fact that there are no draft versions of the records available in the database (probably because in Strapi v4 it is one and the same record).

### Steps to reproduce the behavior

1. Follow the [export documentation](https://docs.strapi.io/dev-docs/data-management/export) on a v4 instance
2. Follow the [import documentation](https://docs.strapi.io/dev-docs/data-management/import) on a v5 instance

### Expected behavior

Would it be an idea to auto create a draft version (containing the data from the published version including relations) when the imported record has an published_at value?

### Additonal notes
I am upgrading Strapi manually hence why I am porting the data manually. 