perf(drizzle): 2x faster document deletion

[AlessioGr]

Currently, db.deleteOne will always result in 2 db calls: finding the document, then deleting it.

However, if returning is false and no joins are required for fetching the document we want to delete, we can do this operation in one single db call: delete it while passing the original where query.

If returning is false but joins are required (e.g. due to complex where query referencing other tables), this also slightly optimizes performance by using a narrower select.

Related PR for deleteMany (already merged - simpler, as deleteMany does not return any documents, deleteOne does): #13255

In order to improve code readability, this also changes this PR to call this.findOne to find the document instead of manually calling drizzle APIs. This does add minimal overhead (buildQuery being called twice), but should not introduce additional db calls.

Local API Performance Impact

The speeds up the payload.delete() local API operation, which uses payload.db.deleteOne + returning: false internally. It does not make use of payload.db.deleteMany

=> Unlike the previous PR optimizing payload.deleteMany(), this PR will actually have a noticeable, positive performance impact when deleting documents in the admin panel - especially when using bulk delete

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1211156702717869

[github-actions]

📦 esbuild Bundle Analysis for payload

This analysis was generated by esbuild-bundle-analyzer. 🤖
This PR introduced no changes to the esbuild bundle! 🙌