Published Content Not Reflecting in Table View
### Bug Report: Published Content Not Reflecting in Table View

**Project Details:**
- **Project Name:** Matatini Strapi
- **Version:** 0.1.0
- **Strapi Version:** 5.6.0
- **Node.js Version:** >=18.0.0 <=22.x.x
- **Database Used:** Better SQLite3 (Version 11.3.0)

---

**Bug Summary:**
When publishing content via the Strapi Admin Panel, the content does not reflect as "Published" in the table view. This discrepancy persists despite the content showing as published in the individual entry view.

---

**Steps to Screenshots:**
1. Navigate to the "Region" collection type in the Strapi Admin Panel.
2. Create a new entry with the name "Aotea."
3. Save the entry as a draft.
4. Publish the entry.
5. Return to the table view for the "Region" collection.

---

**Expected Behavior:**
The table view should update to reflect the published status of the content.

---

**Observed Behavior:**
The content remains listed as "Draft" in the table view, even though the entry displays as "Published" in the individual entry view.

---

**Screenshots:**
![Screenshot 2024-12-23 at 10 33 27 AM](https://github.com/user-attachments/assets/86d5b398-97f0-49b8-9c07-5db2c3d913c2)
![Screenshot 2024-12-23 at 10 32 59 AM](https://github.com/user-attachments/assets/82e1cba6-b48d-44a0-aacb-ba4b2aa2f6a7)
![Screenshot 2024-12-23 at 10 32 51 AM](https://github.com/user-attachments/assets/22b905f3-2f9e-47ff-8597-f78ce0cbf52b)


---

**Environment Details:**
- **Dependencies:**
  ```json
  {
    "@strapi/plugin-cloud": "5.6.0",
    "@strapi/plugin-users-permissions": "5.6.0",
    "@strapi/strapi": "5.6.0",
    "better-sqlite3": "11.3.0",
    "react": "^18.0.0",
    "react-dom": "^18.0.0",
    "react-router-dom": "^6.0.0",
    "styled-components": "^6.0.0"
  }
  ```
- **Dev Dependencies:**
  ```json
  {
    "@types/node": "^20",
    "@types/react": "^18",
    "@types/react-dom": "^18",
    "typescript": "^5"
  }
  ```

---

**Additional Context:**
- The API response correctly shows the `publishedAt` field with a valid timestamp, but this change is not reflected in the table UI.
- The issue may be related to table view caching or an API call that doesn't fetch updated status values.
- I created another empty project on version 5.6.0, and the same bug appears.
- I have another project running on version 5.4.2, and this issue does not occur there.

