Added query tests for $jsonSchema

[vic-tsang]

This PR contains:

• query tests for $jsonSchema
• BSON type testing framework which tests out all the invalid BSON types
  • the reason why we need to test valid BSON type as well for a parameter is to make sure the author doesn't mistakenly mark a parameter with a wrong valid type (in this case without the valid BSON type tests it's not easy to catch)
  • for valid BSON type, we are only checking if there is no error. We don't check if the operator return the correct value as other tests perform those tests

Ref:

• Issue Add compatibility test for query: element and evaluation operators (7 total) #33

[danielfrankcom]

Comments are on the BSON type enumeration approach, as discussed here. Have not reviewed the $jsonSchema coverage specifically.

[documentdb-triage-tool]

🤖 Auto-triaged by documentdb-triage-tool.

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

Reasoning

component from path globs (test-coverage, test-framework); effort from diff stats (2397+1 LOC, 11 files); LLM: Adds new query test coverage for $jsonSchema operator plus a BSON type testing framework, touching test compatibility files across 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.

[eerxuan]

I think this design is better for the argument testing. My updated design is still complex for argument type testing.

I think it's good idea to not have expected value list here, just verify pass. And separation of passing and failing cases is cleaner.