Improve logging for errors

[andr-ec]

Right now when there’s an error it shows an error like this:

2023-10-30T17:06:25Z app[32874de5a0e5e8] gru [info][17:06:24] ERROR (payload): NotFound: The requested resource was not found.
2023-10-30T17:06:25Z app[32874de5a0e5e8] gru [info]    at findByID (/home/node/app/node_modules/payload/dist/collections/operations/findByID.js:85:23)
2023-10-30T17:06:25Z app[32874de5a0e5e8] gru [info]    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

this doesn’t really help me find where the error is coming from. other than from some call findByID.

Can we improve the logging, so that it's clear that it comes from a rest request, a graphql request, a hook and if so which hook.
Ideally the full trace would be great.

[revnelson]

Even just the collection and ID being queried would be very helpful.

As a workaround, I found the error comes from node_module/payload/dist/collections/operations/findById.js line 72. You can play around with incomingArgs and findOneArgs to print out relevant data. For me, just adding in console.error(incomingArgs?.req?.originalUrl); was enough to find my frontend was hitting /api/users/undefined?depth=1 which allowed me to find the bug in my frontend code that tried to pull user data even if no user ID was present.