Draft/Published labels on collection types appear as "Draft" even when "Published"
<!--
Hello 👋 Thank you for submitting an issue.

Before you start, please make sure your issue is understandable and reproducible.
To make your issue readable make sure you use valid Markdown syntax.

https://guides.github.com/features/mastering-markdown/

Please ensure you have also read and understand the contributing guide.

https://github.com/strapi/strapi/blob/main/CONTRIBUTING.md#reporting-an-issue
-->

## 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: 20.17.0
- NPM version: 10.8.2
- Strapi version: 5.6.0
- Database: mySQL
- Operating system: darwin arm64 / macOS 15.2 + Ubuntu 24 in prod
- Is your project Javascript or Typescript: TS

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

### Describe the bug

Draft/Published labels on collection types appear as "Draft" even when "Published"

### Steps to reproduce the behavior

1. Go to 'Content Manager'
2. Click on 'any collection type'
3. Published items get the "Draft" badge on the table
4. Click on any published item for details, the "Published" badge is shown correctly.

Bug was absent

### Expected behavior

Published items get the "Published" badge on the table

### Screenshots

On the collection list table:
![Capture d’écran 2024-12-23 à 18 19 58](https://github.com/user-attachments/assets/d76c008b-44a2-4a9a-8116-07fc27b45a7a)

In the collection item details:
![Capture d’écran 2024-12-23 à 18 22 03](https://github.com/user-attachments/assets/0367d52d-f222-48a8-8e1e-0fb2572a18d0)


### Code snippets

N/A

### Additional context

Bug was absent from previous Strapi versions (5.4 or 5.5). Appeared recently after upgrading.
Same behavior in dev mode locally (macOS 15.2, MacBookPro M1 Max) and in production on an Ubuntu 24 VPS with the same node/npm versions.