Bulk Delete Leaves One Item

Describe the Bug

Deleting multiple collections always leaves one record behind.

This behaviour is as exactly reported on https://github.com/payloadcms/payload/issues/15100, but that issue was closed due to inactivity.

I deployed as per the one-click Vercel deploy button.

I verified this behaviour on prod (both on Vercel, and locally using pnpm run start, but not when running in dev mode (pnpm run dev).

Link to the code that reproduces this issue

https://github.com/usdevs/nusc-wiki

Reproduction Steps

1. Create at least 2 collections (in my case, I used pages)
2. Select all collections (or multi-select the collections), and delete them.

Which area(s) are affected?

db: vercel-postgres

Environment Info

Binaries:
  Node: 22.14.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  payload: 3.73.0
  next: 15.4.11
  @payloadcms/db-vercel-postgres: 3.73.0
  @payloadcms/drizzle: 3.73.0
  @payloadcms/graphql: 3.73.0
  @payloadcms/live-preview: 3.73.0
  @payloadcms/live-preview-react: 3.73.0
  @payloadcms/next/utilities: 3.73.0
  @payloadcms/plugin-cloud-storage: 3.73.0
  @payloadcms/plugin-form-builder: 3.73.0
  @payloadcms/plugin-nested-docs: 3.73.0
  @payloadcms/plugin-redirects: 3.73.0
  @payloadcms/plugin-search: 3.73.0
  @payloadcms/plugin-seo: 3.73.0
  @payloadcms/richtext-lexical: 3.73.0
  @payloadcms/storage-vercel-blob: 3.73.0
  @payloadcms/translations: 3.73.0
  @payloadcms/ui/shared: 3.73.0
  react: 19.2.1
  react-dom: 19.2.1
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home
  Available memory (MB): 16084
  Available CPU cores: 22