Add applyOps tests

[alinaliBQ]

Add command operator tests for applyOps, including the smoke test. Tests database applyOps behavior, output collection, syntax, and errors. Add the ReplicationTestCase class definition.

• Add compatibility test for applyOps #451

[documentdb-triage-tool]

🤖 Auto-triaged by documentdb-triage-tool.

Applied: compatibility test, enhancement
Project fields suggested: Component test-coverage · Priority P2 · Effort L · Status In Progress
Confidence: 0.85 (mixed)

Reasoning

component from path globs (test-coverage, test-framework); effort from diff stats (1233+0 LOC, 11 files); LLM: Adds new applyOps command test coverage and a new ReplicationTestCase class, expanding compatibility test suite across multiple test files within one component.

If a label is wrong, remove it manually and ping @patty-chow so the rules can be tuned. The bot will not re-label items that already have component labels.

[karthikvarma22]

I believe in Mongo, duplicate insert doesn't fail, it upserts it, so allowAtomic true or false wouldnt matter.

Need a case where we have an op that actually fails, like maybe an 'u' instead of insert., and the earlier op still persists

[alinaliBQ]

Yes you are right. I added a test doc_check_atomic_false_partial_commit where update (u) on non-existent id fails, and then checks doc from previous op perisists. atomic_false_partial_commit checks the error code is returned from invalid u command.