Describe the Bug

When autosave is enabled in Payload CMS, published documents that trigger an autosave end up showing a "draft" status in the document list.
This can be misleading because the document is, in fact, already published — but the interface reflects the presence of a draft version instead of the actual published status.

Link to the code that reproduces this issue

Reproduction Steps

1. Enable autosave for a collection.
2. Publish a document.
3. Trigger an autosave (e.g., by making a change without saving manually).
4. Go back to the document list.

Expected behavior:
The list should reflect the published status of the document, even if a draft version exists.

Actual behavior:
The document appears as "draft" in the list, despite having a published version.

This can be confusing for users who rely on the list to see which documents are live.

Which area(s) are affected? (Select all that apply)

area: ui

Environment Info

Node: 20.12.2
  npm: 10.5.0
  Yarn: 1.22.22
  pnpm: 9.6.0
Relevant Packages:
  payload: 3.31.0
  next: 15.2.4
  @payloadcms/db-mongodb: 3.31.0
  @payloadcms/email-nodemailer: 3.31.0
  @payloadcms/graphql: 3.31.0
  @payloadcms/next/utilities: 3.31.0
  @payloadcms/payload-cloud: 3.31.0
  @payloadcms/plugin-cloud-storage: 3.31.0
  @payloadcms/plugin-nested-docs: 3.31.0
  @payloadcms/plugin-seo: 3.31.0
  @payloadcms/richtext-lexical: 3.31.0
  @payloadcms/storage-s3: 3.31.0
  @payloadcms/translations: 3.31.0
  @payloadcms/ui/shared: 3.31.0
  react: 19.0.0
  react-dom: 19.0.0