Make typescript fail when providing unknown query operator

[vkarpov15]

Summary

Right now providing an unknown query operator like $wrong passes in TypeScript, but throws a runtime error. 937eeb1 fixes a related issue where the error message is inconsistent for numbers vs other schematypes.

269afd9 updates it so Mongoose doesn't use MongoDB Node driver's Condition type, which intentionally allows string signature. Instead, we strip out the string signature so only known query operators are allowed.

Examples

[Copilot]

Pull request overview

This PR tightens Mongoose’s TypeScript query filter typings so that unknown field-level query operators (for example $wrong) fail at compile time, aligning TypeScript behavior more closely with Mongoose’s runtime casting behavior.

Changes:

• Replace usage of the MongoDB Node driver’s permissive Condition type with a stricter condition type that removes the driver’s string index signature from FilterOperators.
• Add a TypeScript type test asserting unknown query operators are rejected.
• Update Number schema query casting to throw a consistent “Can’t use $op with Number.” error and add a runtime test for it.

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.

File	Description
types/query.d.ts	Introduces StrictCondition (via index-signature removal) and applies it to QueryFilter to reject unknown operators in TS.
test/types/queries.test.ts	Adds a type-level regression test ensuring { $wrong: ... } fails to compile for filters.
lib/schema/number.js	Updates Number’s castForQuery() to throw a consistent unsupported-operator error message.
test/types.number.test.js	Adds a runtime regression test asserting unsupported operator usage throws with the expected message.

[AbdelrahmanHafez]

One suggestion, otherwise LGTM

[hasezoey]

LGTM