Add tailable cursor tests

[danielfrankcom]

This change adds tests for general tailable cursor behavior.

The intent here is to cover cross-command behavior and state of the tailable cursor itself, without worrying about command-level input/output validation that is already or will be tested elsewhere.

[documentdb-triage-tool]

🤖 Auto-triaged by documentdb-triage-tool.

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

Reasoning

component from path globs (test-coverage, test-framework); effort from diff stats (967+0 LOC, 9 files); LLM: Adds new test cases for tailable cursor behavior in the compatibility test suite, expanding coverage without touching production code.

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.

[yshanhu]

This change adds tests for general tailable cursor behavior.

The intent here is to cover cross-command behavior and state of the tailable cursor itself, without worrying about command-level input/output validation that is already or will be tested elsewhere.

For type validation, are these tested elsewhere?
If not, can we add some typeMismatch tests here for tailable and awaitData?

e.g.

db.runCommand({find: "capped_test", tailable: "true"}),
db.runCommand({find: "capped_test", tailable: 1}),
db.runCommand({find: "capped_test", tailable: true, awaitData: "true"}),
db.runCommand({find: "capped_test", tailable: true, awaitData: 1})

[danielfrankcom]

...
For type validation, are these tested elsewhere? If not, can we add some typeMismatch tests here for tailable and awaitData?
...

I would expect these kind of syntax/type tests to live in documentdb_tests/compatibility/tests/core/query-and-write/commands/find which has not been tackled yet. This is similar to the discussion for collation in #191. imo the syntax tests should live with the tests which are verifying the other options for a specific command, and we should only cover general machinery in these shared directories.