fix(db): preserve operation context and honor ignore_errors on upsert retry

[ar2rsawseen]

What

In the db write wrapper's duplicate-key retry path, the retried attempt re-captured the retry closure's own (empty) arguments via copyArguments. As a result:

• the error log for a failed retried upsert carried no operation context ({"name":"updateOne","args":[]}), making such entries impossible to attribute to a call site
• the ignore_errors: [11000] option could never be detected on the retried attempt, so intentionally-racy upserts (e.g. uid allocation on concurrent first requests, which is designed to collide and recover via request restart) were logged as ERROR despite the caller declaring the error expected

Changes

• capture the original call arguments once per operation and pass them through to the retry closure (also fixes findAndModify remove-result handling on retry, which reads data.args[3])
• read options from the correct argument position for findAndModify (args[3], not args[2]), so ignore_errors is honored there as well
• log ignored expected errors at debug level instead of dropping them silently, so a trace remains available for diagnostics

Unexpected duplicate-key errors (callers that do not pass ignore_errors) are still logged as ERROR, now with full operation context on both the first and the retried attempt.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR fixes the duplicate-key (11000) upsert retry path in the MongoDB write wrapper so that retried attempts preserve the original operation context (method + args) and correctly honor options.ignore_errors—including for findAndModify, whose options live at args[3].

Changes:

• Capture original call arguments once per write operation and reuse them across retries to preserve operation context and option detection.
• Correctly locate findAndModify options at args[3] (vs args[2]) so ignore_errors is respected consistently.
• Log expected/ignored duplicate-key errors at debug level (instead of suppressing error logs entirely), while still logging unexpected ones as ERROR.