Add $geometry tests

[PatersonProjects]

This PR adds the compatibility test for the $geometry geospatial specifier

Ref: Issue #32

[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.82 (mixed)

Reasoning

component from path globs (test-coverage); effort from diff stats (1363+0 LOC, 7 files); LLM: Adds new compatibility test coverage for the $geometry geospatial specifier, expanding test-coverage under documentdb_tests/compatibility/tests.

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]

Most of the test cases are testing $geometry's container like $geoWithin or $geoIntersects. Those are duplication. This folder should focus on $geometry input validation and GeoJson types. Just use one container in command ($geoIntersects"), don't use others.

[PatersonProjects]

All tests now use geoIntersects, removed the index test file as that is out of scope for geometry, some of the tests like point boundaries are arguably also out of scope, but they do require geometry's use and it looks like PR #232 for geoIntersects does not duplicate them so I've kept them here for now.