Fix Issue #202: Add $bitAnd operator expression compatibility tests

[krishnasai453]

Description

This PR resolves failing compatibility tests for the $bitAnd operator in test_expression_bitAnd_additional.py.

Why this is needed

Under MongoDB and DocumentDB specifications, the $bitAnd aggregation operator only supports int and long operands. Passing an array expression (such as [["$a", "$b"], 3]) or an object expression (such as [{"x": "$a", "y": "$b"}, 0]) evaluates to array/object structures, which are non-numeric types. These operations should fail with a type mismatch rather than succeed.

What changed

• Updated ARRAY_EXPRESSION_TESTS and OBJECT_EXPRESSION_TESTS in test_expression_bitAnd_additional.py to expect TYPE_MISMATCH_ERROR (code 14) instead of assuming successful evaluation.
• Forwarded the error_code parameter to assert_expression_result in test_bitAnd_expression_additional.
• Removed the untracked template file test_expression_bitAnd_testing_strategy.txt.

How to test

Run the bitwise operator tests locally:

pytest documentdb_tests/compatibility/tests/core/operator/expressions/bitwise/bitAnd/test_expression_bitAnd.py 
pytest documentdb_tests/compatibility/tests/core/operator/expressions/bitwise/bitAnd/test_expression_bitAnd_additional.py

[krishnasai453]

Hi @ this is my first contribution to this project. I've fixed issue #202 by correcting the additional compatibility tests for the $bitAnd expression operator. Because $bitAnd only accepts numeric integer and long operands, array and object inputs are now properly asserted to reject with a type mismatch error (TYPE_MISMATCH_ERROR).
Would appreciate a review when you have time!

[documentdb-triage-tool]

🤖 Auto-triaged by documentdb-triage-tool.

Applied: compatibility test, bug
Project fields suggested: Component test-coverage · Priority P2 · Effort M · Status Needs Review
Confidence: 0.30 (deterministic)

Reasoning

component from path globs (test-coverage); effort from diff stats (126+0 LOC, 2 files); LLM failed: Invalid response body while trying to fetch https://api.anthropic.com/v1/messages: Premature close

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.